For hunters
Plan your Worked All RI hunt
Work toward POTA's Worked All RI award by hunting Rhode Island's 61 current references. Find parks you still need and plan when to listen.
Already hunted RI parks? Import your POTA Hunted Parks CSV below to personalize your schedule. You can also start a blank checklist or enter the park references you want to hunt. Your past contacts count toward the chase; this checklist is not limited to the event.See the official POTA award details.
No CSV handy? Start with all 61 parks remaining and check them off as you work them.
Build a schedule from park references
Your all-time RI checklist
0 of 61 Rhode Island parks hunted
Plan your event
Your remaining-parks schedule
Checking the event schedule for your remaining parks…
Track your all-time RI history using a POTA import, your manual choices, or both. Check a park after you work it. This changes your checklist; official POTA credit comes from activator logs.
Remaining
No remaining parks match this search.
Hunted
No hunted parks match this search.
Importing a new CSV keeps your manual choices. Reset returns to your latest import, or to all parks remaining if you started blank. Clear removes the import and manual choices from this browser only.
Import POTA CSV
Personalize your hunt
Import your official Hunted Parks export
- Open POTA My Statsand sign in if needed.
- Beside Hunted Parks, choose Export CSV to download
hunter_parks.csv. - Return here and choose or drop that file. Import begins immediately.
If POTA asks you to sign in, finish signing in, return here, and use Open POTA My Stats again.
Choose or drop hunter_parks.csv
CSV only, up to 5 MB. The file never leaves this browser.
Your CSV stays on this device. Your checklist is saved in this browser only.
Privacy details
RI POTA does not upload or retain your CSV, callsign, worldwide history, QSO counts, or dates. Only the RI reference IDs in your latest import, manual checkbox choices, schema version, checklist start time, and import time are saved in this browser. We record coarse, anonymous feature use—such as whether an import succeeded or the personal schedule was opened—using a random event-specific browser ID. Custom analytics is skipped when Global Privacy Control or Do Not Track is enabled.