Hi everyone! 👋
I’m excited to introduce HamTrax - a ham radio logging and tracking app I’ve been building.
What is HamTrax?
- Modern web-based logging for amateur radio contacts
- Built with React, TypeScript, and Firebase
- Mobile-friendly design
- Coming soon to hamtrax.com
I’m a ham myself (KF0NYG) and wanted to build something that fits how I actually operate. Still in development but making progress!
Would love to hear what features the community would find most useful. What’s missing from your current logging workflow?
73 de KF0NYG 📻
Thanks for reporting this critical issue, @mauvehed (KØMVH)! We take iOS compatibility very seriously. Could you share more details about your testing?
- Which iOS version were you using?
- What specific browsers did you try? (Safari, Chrome, Firefox, etc.)
- Any error messages or specific behaviors you noticed?
We want to ensure HamTrax works seamlessly across all platforms. Your detailed feedback will help us track down and fix these compatibility problems.
73 de KF0NYG
Does it have the ability to import contacts from a variety of other formats, namely from QRZ?
Great question! QRZ contact import is definitely on the roadmap. Right now HamTrax is focused on getting the core logging experience solid, but importing from QRZ (and other formats like ADIF) is a high priority feature.
The goal is to make it easy to bring your existing contacts in and keep things synced. What other import sources would be useful for your workflow?
73!
My thoughts mainly surround the initial setup as to have the same data in HamTrax as in QRZ on first use. QRZ is my final stop, but that’s just me. I’m sure there are as many workflows as there are users.
I’ve used a couple of different softwares (full disclosure, I have yet to try HamTrax) and there always seems to be a quirk somewhere along the line. I always wondered if the input screen could be made modular (for any software) so we can input the data in the order which best suits our needs.

