SKU: 69704444616
yellow rattle wildflower seeds

yellow rattle wildflower seeds Yellow Rattle (Rhinanthus minor) | Wildflower Seed

Sale price$25.66 Regular price$28.51
Save 10%

Pay in installments of $7.13 with ShopPay, AfterPay and Klarna

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Sep 7 - Sep 12

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

yellow rattle wildflower seeds Yellow Rattle (Rhinanthus minor) | Wildflower SeedPlease visit our sister site British Wildflower Meadow Seeds if you want less seed than advertised here or if your intended purchases come to under our 100 basket minimum. Yellow Rattle (Rhinanthus minor) Seed Yellow rattle (Rhinanthus minor) is an attractive, partly parasitic ("hemi parasitic"), annual wildflower of short grasslands. "Partly", because it photosynthesises. It's part of the Figwort family, and used to be widespread across the UK on

Please visit our sister site British Wildflower Meadow Seeds if you want less seed than advertised here or if your intended purchases come to under our £100 basket minimum.

Yellow Rattle (Rhinanthus minor) Seed

Yellow rattle (Rhinanthus minor) is an attractive, partly parasitic ("hemi-parasitic"), annual wildflower of short grasslands. "Partly", because it photosynthesises. It's part of the Figwort family, and used to be widespread across the UK on mostly neutral soils. Although it's still found across the country, including in the Machair, it's now much less common. It's appearance is variable; we think there are at least 6 sub-species of it in the UK.

Once Yellow rattle is established it can reduce the vigour of many grasses by up to 50%, thus benefiting other sown wildflowers - check out our blog on how to grow and manage it. Once it dies back, each Rhinanthus plant leaves a space for wildflowers to fill too. It does need full sun, however, and even Yellow rattle will be shaded out by more vigorous grasses on fertile soil - it's not the key to all a meadow maker's problems. Having said that, it can work brilliantly in helping to bring wildflowers back into old pasture, although of course it doesn't of itself reduce soil fertility. Yellow rattle also has other unexpected results. For example, ribwort plantain has learnt to retreat away from it, so does tremendously well in swards with a lot of Rhinanthus in as it fills in the space it leaves behind. Clever things, plants.

Rhinanthus is a helpful plant for pollinators too, particularly bumblebees and butterflies, although honeybees find its slightly complicated flowers difficult to access..

Rarity

For obvious reasons farmers were never terribly keen on Yellow rattle, although it's apparently tasty for livestock. That said, as it is an annual it's easy to mow out before it sets seed (when it rattles) in July. This was traditionally time to cut the hay; hence its synonym, "Hay Rattle". Its seed has notoriously short viability - you must sow from this season's harvest. It will also disappear in thick, unmanaged sward. The seeds are small and the plants unable to compete with surrounding vegetation early on. Nowadays, silage cuts over the summer stop it from seeding at all. Needless to say, it's much less common than it used to be a hundred years ago.

Appearance

Yellow rattle seeds are light flat discs, designed to be wind blown. They germinate from January and the seedlings become evident in early March, so that they steal a march on the surrounding grasses. Be careful not to mow them out! Once they've got going they are easy to spot, however. The leaves have serrated edges, a bit like a nettle, and in seedlings look rather stiff. The flowers look a little like yellow snapdragons (or little cockscombs, apparently). They're very pretty. The plants grow to around 50cm tops.

Buying

Yellow rattle seed must be sown from summer to the year end, as it needs to be chilled to trigger its germination the following spring. We recommend adding the seed to a newly established meadow after its first season. As it doesn't last the seeds need to be as fresh as possible. It also reacts badly to being badly handled - it's tricky to process properly. You need to be careful where you source it from. Our Rhinanthus seed is freshly harvested from meadows in various locations around England. We have it tested once it has been harvested and cleaned to check on the seeds' viability, and require viability over 90%. 

Sowing Seed

The time to seed Yellow rattle is between harvest and the end of December. Like some other wildflower species, it needs to get cold to trigger germination - "vernalization". Sow by hand onto existing sward, at a rate of up to 1g per square metre. It's expensive stuff, so you might want to use a lower rate or just seed some areas and wait for it to spread. It's really important that the existing grass is cut VERY short before seeding and, if necessary, chain harrowed or scarified to get rid of any thatch. Ideally you should see 50% earth. The seeding rate is very low, so you might want to add sand or similar to bulk it out. Once sown, either walk or lightly roll in, or use livestock to tread in the seed and make sure it's in good contact with the earth.

Management

Yellow rattle is a plant of short grassland - if the grasses surrounding it are allowed to grow long and rank it won't be able to compete. Once you've taken a hay cut, typically from July to late August, it's important to keep the grass lightly grazed or cut (removing cuttings) over the winter. Stop cutting in March, or you'll chop the heads off the young seedlings!

Our Seed For Sale

We sell Yellow Rattle seed from 500g, and sell smaller quantities at our sister website: BritishWildflowerMeadowSeeds.co.uk.

The Rhinanthus minor seed we sell is freshly harvested and processed to avoid damage and low germination. We also test it and require at least 90% viability from our harvesters. We currently sell seed from sites in Somerset and Dorset, Shropshire and the Midlands. These sites are generally calcareous or neutral grassland.

We typically deliver from August to December.

We strongly recommend reading up on meadows before buying Yellow Rattle seed. Although our Rhinanthus seed has high germination rates, you need to be careful about initial care and establishing an annual regime. Don't be put off though - once you get the hang of it it's pretty straightforward, so long as you follow instructions!

Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. Standard Shipping : 3-10 business days
  • If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
  • We offer a 30-day return/exchange service after receiving.
  • Final sale items are not eligible for returns or exchanges.
  • To process your return/exchange, please contact us at [email protected]
  • Please click here for more details>>> Return & Exchange Policy
SKU: 69704444616

Discover Niche Categories That Outsell yellow rattle wildflower seeds

Top-Converting Item to Boost Your Average Order

4.4 ★★★★★
Based on 27 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
A
Amazon Customer
Houston, US
★★★★★ 5
This is a "Go-To" for thinking about Cloud Challenges.
Format: Paperback
Delivering and managing fully realized applications in the cloud is different. Different approaches to classic engineering problems than traditional On Premise development and different ways of thinking through the problems of "always available" solutions. I've been in the software delivery business a long time, and with the cloud emerging, for good and ill: I understand the problems, but may be just a little set in my ways. I find this book helps me re-frame challenges in a way that aligns with the strengths of cloud computing. Solve the same problems faster, by thinking about them differently. I'm finding "97 Things Every Cloud Engineer Should Know" great for re-centering my expectations about Cloud Native development and deployment of assets. I started reading it cover to cover over the Christmas Holiday but now i just pick it up and look for the group of essays about exactly the problem I'm wrestling with. P.S. I'm heartened by the editors commitment to Black Lives Matter and Rule of Law. Mentioned only to balance the concerns from another review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on January 24, 2021
C
Verified Purchase
cloud-learner
Pawtucket, US
★★★★★ 3
have some good contents but too general
Format: Paperback
The book covers some good points, but overall, it's too general.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on June 28, 2024
E
Verified Purchase
Engineer Dude
Dallas, US
★★★★★ 3
Why Politics in a Tech Book????
Format: Kindle
Well... I'm surprised to see the book blatently calls out its dedication to Black Lives Matter, which is in all caps so I assume it's referring to the political organization. It goes on to speak of 2020 being the year of an "awakening of injustices of systematic racism"... I thought I was buying a technical book??? Had I known this political bs was included I wouldn't have purchased it! However, I bought and I'm still reading it. If the politics goes away and the TECHNICAL content is good I'll update my review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 13, 2020
P
Verified Purchase
PeaceBee
Lake Worth, US
★★★★★ 2
Not good use of time
Format: Paperback
It’s not clear who this book targets - neither experts nor novice will benefit. There are expert perspectives, only few of these are helpful, rest are too generic to be of any use. For instance the last entry is one an engineer who shares how she went from zero to expert in cloud engineering in six months but fails to mention a single resource or pathway for others to follow.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on April 2, 2022
N
Nilendu Misra
Whiting, US
★★★★★ 3
Uneven compendium of tips and insights, but still very useful
Format: Kindle, Format: Kindle
“In theory, theory and practice are the same. In practice, they are not" is why such bottom-up insights and lessons from the field are the fastest way to learn real life stuff. This series had a GREAT start with "Engineering Management" - I guess because it is way more subjective than Cloud Engineering and offered a variety of non-overlapping POVs. This one is a mixed bag, perhaps because "Cloud Engineering" was perceived amorphously by the authors. The scope was broad - from cloud-native (architecture), to cloud-ready (topology), to cloud-operations, to choosing tech (e.g., Lambda/serverless), to -ilities and economics -- it is like celebrating Halloween, Christmas and Labor Day together in a single long weekend. I would give it 4/+ stars if at least 25% of such a book was "superb", giving 3 because about 10% of the book is. That still leaves 10 solid insights or learning that would otherwise take many failures to learn. And failures, especially in this emerging domain of complexity, is VERY expensive. Would love to see more books like this. Let's summarize some key insights - -- Real-time visibility across the entire DevOps lifecycle is key to winning in cloud. -- Operations, especially operations at scale, is extremely hard. So, wherever possible, use Managed Services. -- Distinguish between "availability" and "uptime" and measure each separately, and concretely. -- In FaaS/Serverless, calling a function synchronously increases debugging complexity. -- Good code is like good joke - it needs no explanation. -- "Building your app or platform on top of the abstractions that a cloud provider gives you does not make the underlying layers stop existing. In many cases, it makes them even more important." That makes the failure modes LESS obvious than we were used to. Therefore having "extreme visibility" into your systems will help "separate the issues at the layer you're focused on from the fundamental system issues". i.e., just because what was under the hood is now even less visible, don't forget them. Many recent "cloud failures" have been in networking fault domains. -- Cloud is not optimized for replacing static infrastructures. -- Containers, service meshes and serverless jumpstart dev productivity but they also change the attack surface of apps and infra. -- "Number of containers that are alive for 10 sec or less has doubled to 22%". 73% of all containers live for 30 minutes or less. -- Adopt an "assume breach" stance for everything. Have a break-glass account. -- Ensure you have a thorough understanding of where and how secrets are secured. -- Grey failures (transient degradation of services) are often worse than complete crashes, since the latter have a short feedback loop. -- Resilience engineering has existed as a sub-discipline within safety sciences. We just recently started applying its concepts in technology. Resilience can be thought of as a "socio-technical system" with Robustness ("system X has property Y that is robust in sense Z to perturbation W"); Reliability (consistent operations or service levels); Rebound (ability to deal with a chaotic situation using structures developed AND deployed BEFORE the chaos). In other words, robustness protects systems against a SPECIFIC type of failure mode. When a system is robust in many dimensions, it approaches good resilience to failure. -- Resilience is something you "do", not something you "have". Resilience is a verb. -- Moving from one class of nines to the next is 10 times more expensive. -- Production System really means "system that someone else, anyone else, can hold you accountable for". -- Most common theme across incidents is that something, somewhere was surprising. -- Incidents are unplanned investments...your challenge is to maximize ROI. -- We used to think of scale in two dimensions - horizontal (more) and vertical (bigger). In cloud, think of "scale out" (when demands increase) and "scale in" (when demand decreases). -- Architecture diagram is also a map of failure modes. -- Async communication is a friend of Cloud Reliability. -- Test in production is a competitive advantage. The complexity of traffic patterns going through high-scale production systems is increasingly harder to reproduce in a controlled env. -- Hundreds of open issues is fine, but if the repo has gone months (or, years!) without a release, THAT is a warning sign. -- It is hard to write good tests for bad code. -- Platforms come and go. But first principles and patterns will always exist, because they are the ones and zeros.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on November 6, 2023

recommand products