What does a trail counter actually count?
A counter counts passes: something crossed its beam or sensor. A pass is not a person. One hiker on an out-and-back trail passes twice. Two people walking side by side may count as one. Depending on the counter and where it is mounted, a dog, a cyclist or a deer may count too.
That doesn't make the data useless. It means you report it as what it is, "counter passes," not "visitors."
How do you clean up trail counter data before you report it?
- Export daily totals from the counter's software as a spreadsheet or CSV file, and keep that original file untouched.
- Look for gaps: zeros or missing days that shouldn't be there, such as a dead battery, snow over the sensor or a damaged post. Mark them; don't fill them with guesses.
- Look for spikes: a race, a work crew walking back and forth, a sensor fault. Note what happened, and leave the count as recorded unless you can explain a change.
- Count the days with data in each month, so a reader knows how complete each month is.
How do you turn counter passes into an estimate of people?
Only with a check you did yourself. Sit near the counter for a few set hours on different days, tally the people who pass, and compare your tally with the counter for the same hours. That ratio tells you roughly how passes relate to people on your trail.
If you use it, report both numbers: the raw passes, and the estimate with the ratio and when you measured it. Without a check like this, report passes and leave it there.
Can you add trail counter numbers to register sign-ins?
No. They overlap: many people who sign the register also walk past the counter. Adding them counts the same hikers twice, and a careful reviewer will notice.
Report them side by side instead. The counter tells you how busy the trail is. The register tells you who those people are and where they came from. Together they make a strong answer.
What should a trail counter report look like?
One row a month, with each source in its own column and no total across them:
| Month | Counter passes | Days with counter data | Register sign-ins | QR check-ins |
|---|---|---|---|---|
| May | 1,812 | 31 of 31 | 164 | 38 |
| June | 2,645 | 26 of 30 | 233 | 61 |
Under the table, add a short method note: where the counter is, what it counts, which days are missing and why, and that the columns are not added together.
How do you explain gaps and partial years?
Say them plainly. "The counter was down June 3 to 6 after a battery failure" is better than an unexplained dip in a chart. If the counter went in partway through the year, label the year as partial ("counter installed in May") rather than comparing half a year with a full one.
For the register side of the report, see how to get visitor numbers for a grant application.
Or let Public Lands Log do it
Public Lands Log turns guest books, QR check-in signs, kiosk sign-ins and trail counter files into visitor numbers by month, where visitors came from, a live map and funder-ready reports.
- Import the counter's CSV export. Its counts sit next to your guest-book and QR check-in numbers, so you can report them side by side.
- Photograph or scan the trail register pages. We read each page, and your staff check the sign-ins against the photo before anything counts.
- Put up a QR sign where there is no desk. Print it at home; visitors scan it with the phone camera, with no app and no account, and the hometown question is optional.
30 days, 150 pages, no card. After the trial, Standard is $490 a year or $49 a month. Start by January 31, 2027 and it is $390 a year for as long as you stay subscribed. See pricing
See it working first: here's a live map from a visitor center in Omaha, Nebraska, counts only and never names.
Questions about trail counter reports
Why doesn't my trail counter number match the trail register?
They measure different things. The counter counts passes, often two per hiker, including people who never stop. The register counts only the people who choose to sign. Both are true, and neither is the total number of visitors.
Should I divide counter passes by two for an out-and-back trail?
Only if you have checked it. Some people loop, turn back early or pass more than twice. A count by hand at the counter tells you the ratio on your trail. If you divide, say so in your method note.
What do I do about days when the counter wasn't working?
Mark them as missing, show how many days each month has data, and don't fill them with guesses. If you estimate a missing stretch, label it as an estimate and show how you got it.
Can I report counter passes as visitors?
Report them as counter passes, with a line saying what they include. Calling them visitors invites the first question a reviewer will ask: how many of those are the same person?