Pest Trap Catch Rate Calculator

Enter monitoring details

Use consistent trap placement and counting rules.

Fields marked * are required.

Pest type *

Example: aphids, thrips, whiteflies.

Trap type *

Choose the style you used in the garden.

Total catch counted *

Sum of insects caught during the window.

Number of traps *

Count only active traps used in monitoring.

Monitoring days *

Days between first and last count.

Area covered (m²) *

Approximate monitored bed or greenhouse area.

Trap efficiency (0.10–1.00)

Lower values increase adjusted pressure estimate.

Lure or adhesive age (days)

Older lures often catch fewer insects.

Temperature (°C)

Optional: use average during the window.

Humidity (%)

Optional: affects activity for many pests.

Low pressure threshold (CTD)

Below this is typically routine monitoring.

High pressure threshold (CTD)

At or above this, take corrective action.

Notes (optional)

Include crop, location, and any unusual conditions.

Reset

Formula used

The core metric is catch per trap-day (CTD), which standardizes catches across different trap counts and monitoring windows.

CTD (raw) = Total catch ÷ (Number of traps × Monitoring days)
Catch per 100 m² per day = (Total catch ÷ (Area m² ÷ 100)) ÷ Monitoring days
CTD (adjusted) = CTD (raw) ÷ Efficiency ÷ Lure factor ÷ Weather factor (adjusts upward when catches are suppressed)

Adjustment factors are optional and designed for trend comparison. For strict scouting logs, rely on the raw CTD and keep methods consistent.

How to use this calculator

Place traps at consistent height, spacing, and orientation.
Count captured pests at the same time of day when possible.
Enter your total catch, trap count, monitoring days, and area.
Optionally enter efficiency and lure age for adjusted comparisons.
Review pressure level, then refine thresholds for your crop.

Example data table

Sample monitoring records for a small garden plot.

Date range	Traps	Days	Total catch	Area (m²)	CTD (raw)
Apr 01–Apr 07	6	7	45	120	1.071
Apr 08–Apr 14	6	7	62	120	1.476
Apr 15–Apr 21	8	7	54	160	0.964
Apr 22–Apr 28	8	6	91	160	1.896
Apr 29–May 05	10	7	155	200	2.214

Use the example above to see how CTD stays comparable even when trap count changes.

Monitoring window design

A catch rate is only as reliable as the monitoring window. Keep the interval consistent, such as 7 days, and record the start and end dates. When windows vary, totals become misleading because activity can spike after irrigation, pruning, or warm nights. The calculator converts totals into trap-days so the value stays comparable.

Normalizing by trap-days

Catch per trap-day (CTD) is calculated as total catch divided by traps multiplied by days. For example, 60 pests across 8 traps for 6 days equals 60 ÷ (8 × 6) = 1.25 CTD. This is useful when you add traps midseason or when a storm destroys a few cards. CTD keeps decisions tied to intensity, not logistics. To reduce noise, use at least 4 traps per zone and avoid counting non-target insects. If one trap is knocked over, exclude it and reduce the trap count accordingly. A 3-week average highlights trends better than single-week peaks.

Adjusted catch rate inputs

Optional adjustments help compare weeks when capture is suppressed. Efficiency reflects placement and trap performance; a value of 0.80 assumes you caught 80% of what the trap could capture. Lure or adhesive age reduces capture over time, so older materials are corrected upward. Weather factors account for changes in insect activity with temperature and humidity.

Threshold setting for action

Use thresholds to translate CTD into response levels. Start with conservative values, then tune them using crop tolerance and damage history. Many gardens treat values under 1.0 as routine, 1.0–5.0 as watchful, and above 5.0 as urgent. The goal is not perfection, but consistent triggers for scouting and intervention.

Recordkeeping for seasonal comparisons

Log crop stage, cultivar, nearby flowering plants, and control actions. Pair trap data with leaf inspections and note beneficial insects. Over several weeks, plot CTD alongside interventions to see lag effects. With clean records, you can compare spring versus late summer pressure and justify changes in trap density or replacement frequency. Record trap height and orientation when shifting crops.

FAQs

1) What does catch per trap-day mean?

It is the average pests caught by one trap in one day. It standardizes totals across different trap counts and monitoring periods, so weekly results remain comparable.

2) Should I use raw or adjusted CTD for decisions?

Use raw CTD for strict trend tracking when your setup is consistent. Use adjusted CTD when traps, lures, or weather likely reduced capture and you need a fair comparison between weeks.

3) How do I choose trap efficiency?

Start with 0.90 for well-placed traps and 0.70–0.80 if traps are shaded, dusty, or too low. Keep the same assumption for a season unless you change trap placement or type.

4) Does lure age matter for sticky cards?

Yes. Dust, sun, and moisture reduce adhesion over time. If cards are older than a week in harsh conditions, the adjusted rate can better reflect pressure than the raw count.

5) Why include catch per 100 m² per day?

It normalizes results by area, which helps compare different beds or greenhouse zones. It is especially useful when trap density changes between locations or seasons.

6) How often should I replace traps?

Replace when surfaces are covered, dusty, or no longer sticky, or when pheromone lures exceed their labeled life. Many gardens refresh sticky cards every 7–14 days during peak pressure.

Notes and good practice

Replace sticky cards when dust or debris reduces adhesion.
Record trap position changes; relocation affects trend accuracy.
Confirm pest identity; some insects are beneficial or non-target.
Combine trap data with leaf inspections for best decisions.