The view is a tabbed collection of tables, each table corresponding to one APRS-receiving port on the system, showing the traffic received by that port. For the total channel traffic, plus each contributing station, the table reports the percentage of the available channel bandwidth used (based on the configured channel baud rate, assuming standard AX.25, not FX.25 or other modulation schemes), the number of packets seen, the nmumber of seconds of channel usage, and the types of packets sent. All these statistics are over the configured period of elapsed time. The types are reported as a series of characters for the different types (underscores indicate the absence of a type of traffic, and lower-case letters indicate only digipeated copies of packet types rather than the original packets):
| character | meaning |
|---|---|
| ? | unknown types of packets (including connected-mode) not categorizable in the below categories |
| P | position packets (including Mic-E and Maidenhead), excluding weather reports with position |
| O | object and item reports |
| S | status reports (including capability responses) |
| X | text messages |
| W | weather messages (including position reports for weather stations) |
| T | telemetry messages (including position messages with Base-91 telemetry) |
| I | invalid messages (syntax error, unrecognized type, etc.) |
| E | all other types of APRS messages |
Note that the table does not report the amount of channel bandwidth wasted due to collisions, as the TNCs (software or hardware) do not report collision intervals. It is unlikely that a channel is capable of exceeding 50% capacity unless a strict discipline such as timeslotting is used by all stations to avoid collisions.
If the expert-mode Configuration dialog's Behavior tab specifies that Aloha circles should be calculated for the APRS-IS feed, then a tab will be added here to display the received APRS-IS traffic.