Home › Log analysis
Analyse a log
Drag an ADIF or Cabrillo file here and see what's in it: QSOs per band, mode, year and prefix, the DXCC entities worked, the locators on the map, dupes, and for contest logs also the file header, the hourly rate and the received exchange. Plus the way back to Cabrillo for your log submission.
Drop an ADIF or Cabrillo file here or
The file isn't uploaded. Only “Keep” stores the analysis on afu.tools, and the contacts themselves only with the tick box next to it.
From the file header
What the contest logger wrote at the top of the Cabrillo file. The organiser bases the scoring on this, not on the contacts alone.
Distribution
Bands
Modes
Years
Prefixes
Rate per hour
Received exchange
Entities worked
| Entity | Prefix | Continent | QSOs | Bands | last |
|---|
Check callsigns
Check the German callsigns in the log against the Bundesnetzagentur (BNetzA, German regulator) list. Whatever is missing there is usually a typo while logging, a special callsign or a club station without an entry.
Where the other stations were
One dot per locator from the log, bigger with more QSOs. For contacts without a locator the centre of the DXCC entity doesn't count: what isn't in the log isn't made up here.
Dupes
The same station on the same day on the same band in the same mode. In a contest it doesn't count twice; in a logbook it's usually a slip when merging two files.
| Callsigns | Date | Band | Mode | Times |
|---|
All contacts
| Date | Time | Callsigns | Band | Mode | Report | Locator | Entity |
|---|
Pass it on
As CSV
The processed contacts as a table, for a spreadsheet or your own analysis. Includes the assigned entity too.
As Cabrillo
For your log submission after a contest. You fill in the header lines here, the contacts come from the log. Read it before sending: every set of rules wants the details slightly differently.
Keep
Stores this analysis on afu.tools and gives you a link to it: the numbers, bands, modes and entities. It can only be seen via the link, never in a list. If you're signed in, you'll also find it in your account, on another device too.
Without the tick the log stays on your computer. With the tick you can later also filter the stored analysis, download it as CSV and convert it to Cabrillo, including the map and dupe check.
This makes your log leave this computer. Callsigns, times and locators of the other stations are then stored with us, and nobody asked them. Only tick it if that's fine with you. You can delete it any time.
Saved from this browser:
What the page does with your log
It shows it to you and forgets it as soon as you close the page. Only “Keep” stores the analysis with us (the numbers, the individual contacts only with the tick box next to it, never in a public list) and gives you a link to it; you can delete it any time.
What gets read
ADIF in the usual form: header up to <EOH>, then contacts, each up to <EOR>. Callsign, date and time, band and frequency, mode, reports, locator and the contest details are analysed. You can drop several files one after the other; they're merged.
Cabrillo is read the same way, meaning the files ending in .cbr or .log that the contest logger writes for submission. The format doesn't define how many exchange fields a line has; the border between the sent and received part is found at the second callsign. A locator in the received exchange lands on the map; lines with X-QSO: were struck out by the sender and don't count.
The entity is derived from the callsign, not from the COUNTRY field in the log: every program fills that field differently. How the mapping works and where its limits are is explained in the prefix lookup.
Cabrillo in brief
Cabrillo is the text format contest logs are submitted in. It consists of a header with details about the station and one line per contact. This page builds both from your log; the exchanged report comes from the STX/SRX fields or their text variants, otherwise only the RST report is set.
Check the file before you submit it. Contest rules differ in their categories, in how zones are given and in which header lines they expect, and no general conversion can know all that.