How One Beekeeper Stopped Losing Hives to Varroa: A Case Study

Every spring, some beekeepers open their hives and find dead colonies. They blame the winter, or the weather, or bad luck. But in a 3-year study, beekeepers using digital treatment tracking had 41% lower winter colony losses than those relying on paper records or memory. The winter wasn't different. The management was.

This case study follows a 40-hive hobbyist, we'll call him Paul, who reduced his winter losses from 60% to 8% after switching to a structured varroa tracking program. The change wasn't dramatic. It was methodical. And the data tells a story that's hard to argue with.

TL;DR

This guide covers key aspects of how one beekeeper stopped losing hives to varroa: a case stu
Mite monitoring should happen at minimum every 3-4 weeks during active season
The 2% threshold in spring/summer and 1% in fall are standard action points based on HBHC guidelines
Always run a pre-treatment and post-treatment mite count to calculate efficacy
Treatment records including product name, EPA number, dates, and counts are required for state inspection compliance
VarroaVault stores all monitoring and treatment data with automatic threshold comparison and state export formatting

Year One: 60% Winter Losses and No Real Explanation

Paul had kept bees for six years when he first contacted us. He ran 40 hives across two apiaries about four miles apart. He was losing roughly 24 hives every winter and spending the spring buying packages to replace them.

He wasn't ignoring varroa. He treated, sometimes twice a year, with Apivar in fall and oxalic acid dribble in late winter. But he was treating on a calendar, not on data. He had no mite counts. He didn't know his infestation rates before or after treatment.

When we first discussed his situation, he said something that stuck: "I always assumed the treatments were working because I was doing them."

That assumption was the problem.

The Diagnostic: What a First Mite Count Revealed

In late April of year one, Paul did his first ever alcohol wash across all 40 hives. The results were alarming.

The average infestation rate across his first apiary was 3.8%. Eleven of the 20 hives were above 4%. Four hives were above 6%.

His second apiary was slightly better, average 2.1%, but still well above any threshold that a spring colony should be at.

He had treated with Apivar the previous October. The mite counts he was seeing in late April should have been close to zero if the treatment had worked. They weren't. Three possibilities: the Apivar hadn't been placed in time to run a full 6-8 week cycle before he removed the strips, the strips had been left in too long and efficacy dropped, or he was dealing with amitraz-resistant mites.

A post-treatment test the following October confirmed resistance. Hives treated with Apivar that fall showed only 64% mite reduction after the full treatment period. The target is 90%+. He'd been relying on a treatment that wasn't working nearly as well as he thought.

The Program Change: Structure Over Habit

Paul switched to a VarroaVault-based tracking program in May of that year. The changes he made were simple, but he made all of them consistently.

Monthly alcohol wash across all 40 hives. Every count logged in the app. Infestation rate calculated automatically.

Seasonal thresholds set in the app. Spring threshold at 2%, summer at 2%, fall at 1%. Alerts fired when any colony crossed the threshold.

treatment rotation. Because Apivar showed low efficacy, he switched to oxalic acid vaporization as his primary treatment. Fall vaporization protocol: 5 rounds at 5-day intervals starting the second week of August, regardless of brood status.

Post-treatment counts. Three weeks after completing any treatment course, Paul did a mite count and logged it alongside the original treatment record.

The first fall under the new program, his post-OA-vaporization counts came back averaging 0.3% across both apiaries. That's the result you're looking for.

The Numbers: Three Years of Mite Count Data

Here's what Paul's mite count progression looked like, showing average infestation rates across 40 hives:

Year 1 (before program):

April count: 3.8% (apiary 1), 2.1% (apiary 2)
No other counts taken
Winter loss: 24 of 40 hives (60%)

Year 2 (first full program year):

April: 1.2% / 0.9%
June: 1.4% / 1.1%
August (pre-treatment): 2.0% / 1.7%
September (post-treatment): 0.4% / 0.3%
Winter loss: 7 of 40 hives (17.5%)

Year 3 (second full program year):

April: 0.7% / 0.6%
June: 0.9% / 0.8%
August (pre-treatment): 1.5% / 1.2%
September (post-treatment): 0.2% / 0.3%
Winter loss: 3 of 40 hives (7.5%)

The trend is clear. And it wasn't magic. It was data.

What Caused the High Losses: The Three-Part Problem

Looking back at Paul's history, his losses came from three problems that compound each other.

First, he didn't know his baseline. Without mite counts, he had no idea that his spring infestation rates were 2-4x the threshold. He thought he was keeping up because he was treating. He wasn't keeping up at all.

Second, his fall treatment was ineffective. The Apivar resistance issue meant his main treatment tool wasn't working. Without post-treatment counts, he never knew. He went into two consecutive winters with colonies that had been "treated" but still had high mite loads. Those are the hives that die.

Third, his timing was wrong. His October Apivar application came after the critical late-August/early-September window when winter bees are raised. Even a fully effective October treatment can't undo the damage done to bees raised in a high-mite environment in August. The bees that will carry the colony through winter need to be raised mite-free. They weren't.

What Changed: Not the Products, the Timing and the Data

Paul didn't find a better treatment product. Oxalic acid has been available to beekeepers for years. What changed was that he had the data to know when to use it, and a post-treatment verification that told him whether it worked.

The August-start vaporization protocol was the single biggest change. By starting his fall treatment in the second week of August rather than waiting until October, he protected the bees that actually mattered: the long-lived winter bees raised in late August and September.

The varroa mite treatment software made the timing hard to miss. Treatment reminders started appearing in his app dashboard on August 10. Post-treatment count reminders fired automatically three weeks after the final vaporization. The structure was built into the system. He didn't have to remember. The app remembered for him.

The ROI: Replacing Packages vs. Tracking Mites

Paul was spending approximately $200 per package to replace lost colonies each spring. At 24 lost hives, that was $4,800 per year in replacement packages alone, not counting the lost honey production from dead hives and weak replacement colonies.

Year 2: 7 lost hives, $1,400 in replacements. Year 3: 3 lost hives, $600 in replacements.

That's a reduction in direct replacement costs of over $4,000 per year. His VarroaVault subscription costs less than his February package order used to.

The mite count tracking app paid for itself in his first spring with fewer packages to buy.

FAQ

What caused high winter losses in this case study?

Three factors combined: no baseline mite counts meant Paul didn't know how bad his infestation levels were; amitraz resistance meant his Apivar treatments weren't achieving the 90%+ mite reduction needed; and his treatment timing (October) came too late to protect the August-September winter bees. Any one of these factors can drive high winter losses. All three together produced a 60% loss rate.

What changed when the beekeeper started using VarroaVault?

The biggest change was moving from calendar-based treatment to data-driven treatment. Monthly mite counts revealed actual infestation rates, seasonal threshold alerts flagged problems early, and post-treatment counts confirmed whether treatments worked. Discovering amitraz resistance through post-treatment data allowed a treatment switch. Changing the timing of fall treatment from October to August protected winter bees during the critical raising window. All of these changes were made possible by having consistent, recorded data.

How quickly did mite levels drop after the program started?

After the first full fall treatment cycle using OA vaporization (5 treatments over 25 days starting in mid-August), post-treatment counts averaged 0.3-0.4% across both apiaries, down from 2.0% and 1.7% pre-treatment. That's an 80%+ reduction in a single treatment cycle. By the second year of the program, spring counts were starting below 1%, which suggests the colonies weren't entering winter with the high mite loads that were compounding from year to year under the previous approach.

How do I know if my varroa treatment is working?

Run a mite count 2-4 weeks after the treatment ends and compare it to your pre-treatment count. The efficacy formula is: ((pre-count - post-count) / pre-count) x 100. A result above 90% indicates effective treatment. Results below 80% should trigger investigation for possible resistance, application error, or reinfestation. Log both counts in VarroaVault to track efficacy trends across treatment cycles.

How often should I check mite levels in my hives?

At minimum, once per month (every 3-4 weeks) during the active season. Increase to every 2 weeks when counts are near threshold or after a treatment to verify it worked. In fall, monitoring frequency matters most because the window to treat before winter bees are raised is narrow. VarroaVault's monitoring reminders can be set to your preferred interval for each apiary.

What records should I keep for varroa management?

Each record should include: date of count or treatment, hive identifier, monitoring method used, number of bees sampled, mites counted, infestation percentage, treatment product name and EPA registration number, dose applied, treatment start and end dates, and PHI end date. State apiarists typically expect this level of detail during inspections. VarroaVault captures all of these fields in a single log entry.

Sources

American Beekeeping Federation (ABF)
USDA ARS Bee Research Laboratory
Honey Bee Health Coalition
Penn State Extension Apiculture Program
Project Apis m.

The Takeaway

Paul's story isn't unusual. It's extremely common. The beekeepers who lose the most hives are almost never the ones who aren't trying. They're the ones who are trying without the data to know whether what they're doing is working.

Sixty percent winter losses became seven percent not because varroa got easier to manage, but because Paul finally knew what his mite levels were, when they crossed thresholds, whether his treatments worked, and when the most important treatment window opened each year.

That's information. And information is what turns beekeeping from hoping to managing.

Get Started with VarroaVault

The information in this guide is most useful when you have your own mite count data to apply it to. VarroaVault stores every count, flags threshold crossings automatically, and builds the treatment history you need for state inspections and effective management decisions. Start your free trial at varroavault.com.