CSV files

CSV (comma-separated values) is the plain-text format the Log files destination writes. CSV files open in spreadsheets, databases and analysis tools. This page lists the columns in each file.

The files are in the phone’s Download/NetworkSurveyData/csv folder. The Log files page (More > Log files) lists them and can share them.

What is CSV?

• Format: Plain text, comma-delimited
• File Extension: .csv
• Structure: One row per record, columns for fields
• Header Row: First row after the comment lines contains field names
• Compatibility: Universal (Excel, Google Sheets, Python, R)

Note

Each file starts with two comment lines (prefixed with #): the app version that wrote it and the CSV format version of that file type. For example:

# Created by Network Survey version=2.0
# CSV Version=0.6.0

The CDR build adds -cdr to the app version (version=2.0-cdr). The CSV version tells a script which column layout of that file type to expect. If your spreadsheet shows the comment lines as rows, skip the first two lines.

Quick reference

File Type	Columns	CSV Version	Description
GSM	23	0.4.0	2G GSM cellular records
CDMA	22	0.3.0	2G/3G CDMA cellular records
UMTS	24	0.4.0	3G UMTS/WCDMA cellular records
LTE	30	0.6.0	4G LTE cellular records
NR (5G)	30	0.5.0	5G NR cellular records
Wi-Fi	30	0.4.0	802.11 beacon records
Wi-Fi clients	18	0.1.0	Wi-Fi client records (NS Scout)
Wi-Fi probe requests	21	0.1.0	Probe request records (NS Scout)
Bluetooth	23	0.3.0	Bluetooth Classic & BLE records
GNSS	25	0.4.0	Satellite navigation records
Phone state	15	0.4.0	SIM and network registration state
Device status	22	0.6.0	Battery and location source info
CDR	17	0.5.0	Call records

File naming

Network Survey creates a separate CSV file for each cellular technology and each record type. YYYYMMDD-HHMMSS is when the file was started, in the phone’s time zone:

Cellular:

craxiom-gsm-YYYYMMDD-HHMMSS.csv
craxiom-cdma-YYYYMMDD-HHMMSS.csv
craxiom-umts-YYYYMMDD-HHMMSS.csv
craxiom-lte-YYYYMMDD-HHMMSS.csv
craxiom-nr-YYYYMMDD-HHMMSS.csv
craxiom-phonestate-YYYYMMDD-HHMMSS.csv
craxiom-cdr-YYYYMMDD-HHMMSS.csv

Other Technologies:

craxiom-wifi-YYYYMMDD-HHMMSS.csv
craxiom-wifi-client-YYYYMMDD-HHMMSS.csv
craxiom-wifi-probe-YYYYMMDD-HHMMSS.csv
craxiom-bluetooth-YYYYMMDD-HHMMSS.csv
craxiom-gnss-YYYYMMDD-HHMMSS.csv
craxiom-devicestatus-YYYYMMDD-HHMMSS.csv

The craxiom-wifi-client- and craxiom-wifi-probe- files hold Wi-Fi clients, which only an NS Scout records. A Scout’s raw frames go to craxiom-wifi-raw-YYYYMMDD-HHMMSS.pcapng files in the same folder; those are pcapng, not CSV.

If two files of the same type start in the same second, the later one gets -1 (then -2 and so on) before .csv. See Log files for when each file is created and when a new one starts.

CSV structure

• Comment lines: metadata about the file (lines starting with #)
• Header row: field names (first non-comment row)
• Data rows: survey records (one per line)
• Delimiter: comma (,)
• Text qualifier: double quotes (") for fields containing commas
• Decimals: latitude, longitude, altitude, speed and accuracy use the phone’s decimal separator, so on a phone set to a language that writes decimal commas (German, French and others) they look like "48,858400", in quotes. Other numeric columns always use a dot. Digits and the minus sign are always plain ASCII, with no thousands separators.

Example LTE CSV:

# Created by Network Survey version=2.0
# CSV Version=0.6.0
deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,mcc,mnc,tac,eci,earfcn,pci,rsrp,rsrq,ta,servingCell,lteBandwidth,provider,signalStrength,cqi,slot,snr,deviceSerialNumber,locationAge,plmn,connectionStatus,cellBandwidthsKhz
2026-10-10T13:58:27.603261-04:00,37.774900,-122.419400,15.58,0,22,NS 1234abc12e56789f 20261010-135821,1,2,310,260,12345,12345678,750,36,-112.0,-9.0,39,true,MHZ_10,T-Mobile,-61.0,11,,-1.0,1234abc12e56789f,4916,310-260,PRIMARY_SERVING,20000;10000

Common fields

These fields appear in most CSV file types:

Field	Description
deviceTime	Timestamp formatted as RFC3339 date-time with timezone (e.g., 2025-10-10T13:58:27.603261-04:00)
latitude	The latitude representing where this survey record was recorded (WGS84 decimal degrees)
longitude	The longitude representing where this survey record was recorded (WGS84 decimal degrees)
altitude	The altitude in meters as Android reports it: height above the WGS84 ellipsoid, not above mean sea level
speed	Device speed in meters per second. 0 when the phone reported no speed or less than 0.1 m/s
accuracy	Horizontal location accuracy in meters (68% confidence radius). A value of 0 indicates there was no available horizontal accuracy
missionId	A unique name for this particular run of a survey. Typically includes the timestamp of when the survey was started, or may contain a user-entered value (format: NS <deviceSerial> <timestamp>)
recordNumber	A counter that goes up by one for each record of the type. All cellular technologies share one counter, and the count does not restart with each file, so the numbers in one file can start above 1 and skip
groupNumber	Groups records from the same scan together. For cellular surveys, each scan of the serving cell and neighbor cells should have the same group number
deviceSerialNumber	The phone’s Android ID, shown as Device serial number in Settings. It changes if the phone is factory reset
locationAge	Age of the location fix in milliseconds when the record was created

About empty values

Some fields may be empty when data is unavailable. For example, ta (Timing Advance) is typically only populated for serving cells, and optional measurements like snr may be empty if the device doesn’t report them. An empty cell means “not reported”, never zero.

Enum fields

Several fields use enumerated values (e.g., lteBandwidth, encryptionType, constellation). See the NS Messaging API for complete lists of valid values for each enum field.

---

Cellular records

PLMN field

The GSM, UMTS, LTE and NR files include a plmn column containing the PLMN identifier in “MCC-MNC” format (e.g., “310-01”). This field preserves MNC leading zeros that are lost in the integer mcc/mnc columns. The legacy mcc and mnc columns are still present but deprecated. Consumers should prefer plmn.

GSM

2G GSM (Global System for Mobile Communications) cellular network records.

File pattern: craxiom-gsm-YYYYMMDD-HHMMSS.csv CSV Version: 0.4.0 Columns: 23

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,mcc,mnc,lac,ci,arfcn,bsic,signalStrength,ta,servingCell,provider,slot,deviceSerialNumber,locationAge,plmn

Field	Description
(common)	Common fields also apply: deviceTime, latitude, longitude, altitude, etc.
mcc	Mobile Country Code (3-digit, e.g., 310). Deprecated: prefer plmn
mnc	Mobile Network Code (2-3 digit). Deprecated: prefer plmn
plmn	PLMN identifier in “MCC-MNC” format (e.g., “310-260”). MCC is always 3 digits, MNC is 2 or 3 digits with leading zeros preserved
lac	Location Area Code (0-65535)
ci	Cell Identity (0-65535)
arfcn	Absolute Radio Frequency Channel Number (valid values defined in 3GPP TS 45.005)
bsic	Base Station Identity Code (0-63), consists of NCC (Network Color Code) and BCC (Base station Color Code)
signalStrength	Signal strength in dBm
ta	Timing Advance (valid range 0-63), indicates distance to tower
servingCell	true if this is the serving cell, false for neighbor cells. If the field is unset then it is unknown
provider	Network operator name
slot	SIM slot number. Numbering does not start at 0 or 1, and can be any arbitrary number

CDMA

2G/3G CDMA (Code Division Multiple Access) cellular network records.

File pattern: craxiom-cdma-YYYYMMDD-HHMMSS.csv CSV Version: 0.3.0 Columns: 22

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,sid,nid,zone,bsid,channel,pnOffset,signalStrength,ecio,servingCell,provider,slot,deviceSerialNumber,locationAge

Field	Description
(common)	Common fields also apply: deviceTime, latitude, longitude, altitude, etc.
sid	System Identification Number (15-bit number)
nid	Network Identification Number (16-bit number)
zone	Registration Zone. A collection of one or more base stations treated as a unit for registration purposes
bsid	Base Station ID (0-65535)
channel	CDMA channel number
pnOffset	Pseudo-Noise Offset (0-511)
signalStrength	Signal strength in dBm
ecio	Energy per chip to Interference power ratio measured in dB
servingCell	true if this is the serving cell. If the field is unset then it is unknown
provider	Network operator name
slot	SIM slot number. Numbering does not start at 0 or 1, and can be any arbitrary number

UMTS

3G UMTS (Universal Mobile Telecommunications System) / WCDMA cellular network records.

File pattern: craxiom-umts-YYYYMMDD-HHMMSS.csv CSV Version: 0.4.0 Columns: 24

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,mcc,mnc,lac,cid,uarfcn,psc,rscp,ecno,signalStrength,servingCell,provider,slot,deviceSerialNumber,locationAge,plmn

Field	Description
(common)	Common fields also apply: deviceTime, latitude, longitude, altitude, etc.
mcc	Mobile Country Code (3-digit, e.g., 310). Deprecated: prefer plmn
mnc	Mobile Network Code (2-3 digit). Deprecated: prefer plmn
plmn	PLMN identifier in “MCC-MNC” format (e.g., “310-260”). MCC is always 3 digits, MNC is 2 or 3 digits with leading zeros preserved
lac	Location Area Code (0-65535)
cid	Cell Identity (28-bit). The RNC-ID is the first 12 bits, and the C-ID is the last 16 bits
uarfcn	Downlink UTRA Absolute Radio Frequency Channel Number (valid range 0-16383)
psc	Primary Scrambling Code (0-511)
rscp	Received Signal Code Power in dBm
ecno	Ec/No ratio in dB (signal quality). The value is negative as the RSCP is smaller than the total received power
signalStrength	Signal strength in dBm
servingCell	true if this is the serving cell. If the field is unset then it is unknown
provider	Network operator name
slot	SIM slot number. Numbering does not start at 0 or 1, and can be any arbitrary number

LTE

4G LTE (Long-Term Evolution) cellular network records.

File pattern: craxiom-lte-YYYYMMDD-HHMMSS.csv CSV Version: 0.6.0 Columns: 30

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,mcc,mnc,tac,eci,earfcn,pci,rsrp,rsrq,ta,servingCell,lteBandwidth,provider,signalStrength,cqi,slot,snr,deviceSerialNumber,locationAge,plmn,connectionStatus,cellBandwidthsKhz

Field	Description
(common)	Common fields also apply: deviceTime, latitude, longitude, altitude, etc.
mcc	Mobile Country Code (3-digit, e.g., 310). Deprecated: prefer plmn
mnc	Mobile Network Code (2-3 digit, e.g., 260). Deprecated: prefer plmn
plmn	PLMN identifier in “MCC-MNC” format (e.g., “310-260”). MCC is always 3 digits, MNC is 2 or 3 digits with leading zeros preserved
tac	Tracking Area Code (0-65535)
eci	E-UTRAN Cell Identifier (28-bit). The Macro eNB ID is the first 20 bits, and the last 8 bits represent the sector
earfcn	Downlink E-UTRA Absolute Radio Frequency Channel Number
pci	Physical Cell Identity (0-503)
rsrp	Reference Signal Received Power in dBm (valid range -140 to -44)
rsrq	Reference Signal Received Quality in dB (valid range -19.5 to -3)
ta	Timing Advance value (valid range 0-1282)
servingCell	true if this is the serving cell. If the field is unset then it is unknown
lteBandwidth	Channel bandwidth enum (one of MHZ_1_4, MHZ_3, MHZ_5, MHZ_10, MHZ_15, MHZ_20)
provider	Network operator name
signalStrength	Overall signal strength in dBm
cqi	Channel Quality Indicator (0-15). Used by the UE to notify the serving cell (eNodeB) about the quality of the downlink channel
slot	SIM slot number. Numbering does not start at 0 or 1, and can be any arbitrary number
snr	Reference Signal Signal-to-Noise Ratio in dB (range -20 dB to +30 dB)
connectionStatus	How the phone is connected to this cell: PRIMARY_SERVING, SECONDARY_SERVING or NEIGHBOR. Empty when the phone did not report it
cellBandwidthsKhz	The channel bandwidth of each carrier the phone’s data connection was using, in kHz, separated by semicolons (for example 20000;10000). Two or more values mean carrier aggregation was active. Only filled on cells the phone was using, and empty when the phone did not report it (which does not mean there was no carrier aggregation)

NR (5G)

5G NR (New Radio) cellular network records.

File pattern: craxiom-nr-YYYYMMDD-HHMMSS.csv CSV Version: 0.5.0 Columns: 30

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,mcc,mnc,tac,nci,narfcn,pci,ssRsrp,ssRsrq,ssSinr,csiRsrp,csiRsrq,csiSinr,ta,servingCell,provider,slot,deviceSerialNumber,locationAge,plmn,connectionStatus,cellBandwidthsKhz

Field	Description
(common)	Common fields also apply: deviceTime, latitude, longitude, altitude, etc.
mcc	Mobile Country Code (3-digit, e.g., 310). Deprecated: prefer plmn
mnc	Mobile Network Code (2-3 digit, e.g., 480). Deprecated: prefer plmn
plmn	PLMN identifier in “MCC-MNC” format (e.g., “311-480”). MCC is always 3 digits, MNC is 2 or 3 digits with leading zeros preserved
tac	Tracking Area Code (24-bit, as defined in 3GPP TS 24.501)
nci	NR Cell Identity (36-bit). The gNB ID is the first 22-32 bits of the NCI
narfcn	Downlink NR Absolute Radio Frequency Channel Number (valid range 0-3,279,165)
pci	Physical Cell Identity (0-1007)
ssRsrp	SS Reference Signal Received Power in dBm (valid range -156 to -31)
ssRsrq	SS Reference Signal Received Quality in dB (valid range -43 to 20)
ssSinr	SS Signal-to-Interference-plus-Noise Ratio in dB (range -23 dB to 40 dB with 0.5 dB resolution)
csiRsrp	Channel State Information (CSI) Reference Signal Received Power in dBm (valid range -140 to -44)
csiRsrq	Channel State Information (CSI) Reference Signal Received Quality in dB
csiSinr	Channel State Information (CSI) Signal-to-Interference-plus-Noise Ratio in dB (range -23 dB to 40 dB with 0.5 dB resolution)
ta	Timing Advance value (valid range 0-3846)
servingCell	true if this is the serving cell. If the field is unset then it is unknown
provider	Network operator name
slot	SIM slot number. Numbering does not start at 0 or 1, and can be any arbitrary number
connectionStatus	How the phone is connected to this cell: PRIMARY_SERVING, SECONDARY_SERVING or NEIGHBOR. A 5G NSA data leg shows as a SECONDARY_SERVING NR cell with servingCell false. Empty when the phone did not report it
cellBandwidthsKhz	The channel bandwidth of each carrier the phone’s data connection was using, in kHz, separated by semicolons. Two or more values mean carrier aggregation was active. Only filled on cells the phone was using; empty when not reported

---

Other technologies

Wi-Fi

Wi-Fi access point records: one row per access point in each Android Wi-Fi scan, or, while an NS Scout is the Wi-Fi source, at most one row per access point per window.

File pattern: craxiom-wifi-YYYYMMDD-HHMMSS.csv CSV Version: 0.4.0 Columns: 30

Android’s Wi-Fi scan results don’t include every field, so for the phone’s own scans these columns are always empty: sourceAddress, destinationAddress, beaconInterval, serviceSetType, supportedRates, extendedSupportedRates, cipherSuites, akmSuites, snr and nodeType. They are kept so the column layout stays the same. Rows from an NS Scout fill them where the access point advertises the value (snr needs the Scout’s noise reading). passpoint is either true or empty.

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,sourceAddress,destinationAddress,bssid,beaconInterval,serviceSetType,ssid,supportedRates,extendedSupportedRates,cipherSuites,akmSuites,encryptionType,wps,channel,frequencyMhz,signalStrength,snr,nodeType,standard,passpoint,bandwidth,deviceSerialNumber,locationAge

Field	Description
(common)	Common fields also apply (note: Wi-Fi does not use groupNumber): deviceTime, latitude, longitude, altitude, etc.
sourceAddress	Source MAC address of the frame
destinationAddress	Destination MAC address of the frame
bssid	The MAC Address of the Access Point
beaconInterval	Beacon Interval, in milliseconds
serviceSetType	Network type enum (e.g., BSS, ESS, IBSS, MBSS)
ssid	UTF-8 encoded network name (may be empty for hidden networks)
supportedRates	Supported data rates in Mbps, separated by semicolons
extendedSupportedRates	Extended supported data rates in Mbps, separated by semicolons
cipherSuites	Encryption cipher suites supported (as defined in IEEE Std 802.11-2012)
akmSuites	Authentication and Key Management suites (as defined in IEEE Std 802.11-2012)
encryptionType	Security type enum (e.g., OPEN, WEP, WPA, WPA2, WPA3)
wps	Wi-Fi Protected Setup enabled (true/false), as defined by the Wi-Fi Alliance
channel	Wi-Fi channel number
frequencyMhz	Center frequency in MHz
signalStrength	Received signal strength in dBm. Empty when Android listed the access point without a measured signal
snr	Signal-to-Noise Ratio in dB
nodeType	Node classification (e.g., AP, STA)
standard	802.11 standard enum (e.g., IEEE80211N, IEEE80211AC, IEEE80211AX, IEEE80211BE)
passpoint	Hotspot 2.0/Passpoint support (true/false). Passpoint is a standard defined by the Wi-Fi Alliance, not IEEE
bandwidth	Channel bandwidth enum (e.g., MHZ_20, MHZ_40, MHZ_80, MHZ_80_PLUS, MHZ_160, MHZ_320)

Wi-Fi clients

Wi-Fi client records, which only an NS Scout records: at most one row per client per window.

File pattern: craxiom-wifi-client-YYYYMMDD-HHMMSS.csv CSV Version: 0.1.0 Columns: 17

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,sourceAddress,bssid,channel,frequencyMhz,signalStrength,snr,frameTypes,deviceSerialNumber,locationAge

Field	Description
(common)	Common fields also apply, except groupNumber
sourceAddress	The client’s MAC address
bssid	The access point the client was heard talking to. Empty when not known
channel	The channel it was heard on
frequencyMhz	Center frequency in MHz
signalStrength	The strongest signal heard from the client in the window, in dBm
snr	Signal-to-noise ratio in dB, when the Scout measured the noise
frameTypes	Every kind of frame it sent in the window, each once, separated by semicolons (e.g., DATA;NULL_DATA;PROBE_REQUEST)

Wi-Fi probe requests

The probe requests behind Wi-Fi clients: at most one row per client and requested network name per window. Written whenever Wi-Fi clients is recorded to Log files.

File pattern: craxiom-wifi-probe-YYYYMMDD-HHMMSS.csv CSV Version: 0.1.0 Columns: 20

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,sourceAddress,destinationAddress,bssid,ssid,channel,frequencyMhz,signalStrength,snr,nodeType,standard,deviceSerialNumber,locationAge

Field	Description
(common)	Common fields also apply, except groupNumber
sourceAddress	The MAC address of the client that sent the request
destinationAddress	The address the request was sent to: the broadcast address, or one access point
bssid	The BSSID field of the request (the broadcast address unless it was sent to one access point)
ssid	The network name the client asked for. Empty for a wildcard request (any network)
nodeType	Always NON_AP_STA: a probe request comes from a client
standard	The newest 802.11 standard the client says it supports in the request (e.g., IEEE80211N, IEEE80211AX), or UNKNOWN

The other columns mean the same as in the Wi-Fi clients file.

Bluetooth

Bluetooth Classic and Bluetooth Low Energy (BLE) records.

File pattern: craxiom-bluetooth-YYYYMMDD-HHMMSS.csv CSV Version: 0.3.0 Columns: 23

The destinationAddress and channel columns are always empty, because Android does not report them for Bluetooth scans.

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,sourceAddress,destinationAddress,signalStrength,txPower,technology,supportedTechnologies,otaDeviceName,channel,deviceSerialNumber,locationAge,addressType,deviceClass,serviceUuids,companyId,mfgData

Field	Description
(common)	Common fields also apply (note: Bluetooth does not use groupNumber): deviceTime, latitude, longitude, altitude, etc.
sourceAddress	Source Bluetooth address (MAC format)
destinationAddress	Destination Bluetooth address
signalStrength	Received signal strength (RSSI) in dBm
txPower	Transmit power level in dBm (from advertisement)
technology	How this record was heard: LE for a Bluetooth LE scan result. Records from Classic discovery show UNKNOWN, because Android cannot tell which radio they arrived on
supportedTechnologies	All technologies supported by the device (enum values). As defined in Bluetooth Spec Vol 1 Part A Section 1
otaDeviceName	Device name from over-the-air advertisement (as defined in Bluetooth Spec Vol 3 Part C Section 3.2.2)
channel	Bluetooth channel number (valid range 0-78, as defined in Bluetooth Spec Vol 2 Part A Section 2)
addressType	Address type enum (e.g., PUBLIC, RANDOM)
deviceClass	Bluetooth device class code (Classic only, hexadecimal, 4 bytes, with leading zeros removed)
serviceUuids	Advertised service UUIDs
companyId	Bluetooth SIG assigned company identifier (hexadecimal, 4 bytes). See the Bluetooth Assigned Numbers document
mfgData	Manufacturer-specific data (hex encoded). Includes company ID prefix (first 2 bytes in little endian order)

GNSS

GNSS (Global Navigation Satellite System) records including GPS, GLONASS, Galileo, and BeiDou.

File pattern: craxiom-gnss-YYYYMMDD-HHMMSS.csv CSV Version: 0.4.0 Columns: 25

The clockOffset, undulationM, hdop and vdop columns are always empty, because the app does not fill them. latitudeStdDevM and longitudeStdDevM both hold the horizontal accuracy Android reports for the location, and altitudeStdDevM its vertical accuracy.

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,groupNumber,constellation,spaceVehicleId,carrierFreqHz,clockOffset,usedInSolution,undulationM,latitudeStdDevM,longitudeStdDevM,altitudeStdDevM,agcDb,cn0DbHz,hdop,vdop,deviceModel,deviceSerialNumber,locationAge

Field	Description
(common)	Common fields also apply: deviceTime, latitude, longitude, altitude, etc.
constellation	Satellite constellation enum (e.g., GPS, GLONASS, GALILEO, BEIDOU, QZSS, SBAS)
spaceVehicleId	The identifier for the space vehicle (SV)
carrierFreqHz	Carrier frequency in Hz utilized by the SV
clockOffset	The receiver clock bias representing the time difference between the GNSS receiver’s internal clock and the true GNSS system time
usedInSolution	A value of true indicates the satellite was used in the position fix. A value of false indicates it was not used. An empty cell means the receiver did not report this satellite in its status
undulationM	The difference between the WGS84 ellipsoid altitude and the Mean Sea Level (MSL) altitude (geoid altitude). A positive value means MSL is above the ellipsoid
latitudeStdDevM	Latitude standard deviation in meters. At a 68% confidence level, the true position is within 1 standard deviation. At 95% confidence, the true position is within approximately 2 standard deviations
longitudeStdDevM	Longitude standard deviation in meters. At a 68% confidence level, the true position is within 1 standard deviation. At 95% confidence, the true position is within approximately 2 standard deviations
altitudeStdDevM	Altitude standard deviation in meters. VDOP is used to estimate the vertical accuracy
agcDb	Automatic Gain Control level in dB (valid range -50.0 to 50.0)
cn0DbHz	Carrier-to-Noise density ratio in dB-Hz (typical range 10-50 dB-Hz)
hdop	Horizontal Dilution of Precision (valid range 0.0 to 50.0)
vdop	Vertical Dilution of Precision (valid range 0.0 to 50.0)
deviceModel	Device model name

---

System files

Phone state

SIM card and network registration state records.

File pattern: craxiom-phonestate-YYYYMMDD-HHMMSS.csv CSV Version: 0.4.0 Columns: 15

deviceTime,latitude,longitude,altitude,speed,accuracy,missionId,recordNumber,simState,simOperator,networkRegistrationInfo,deviceSerialNumber,slot,nonTerrestrialNetwork,locationAge

Field	Description
(common)	Common fields also apply (note: Phone State does not use groupNumber): deviceTime, latitude, longitude, altitude, etc.
simState	SIM card state enum (e.g., READY, ABSENT, PIN_REQUIRED). References Android TelephonyManager SimState
simOperator	The PLMN portion of the SIM’s IMSI. This is the provider that issued the SIM card (5 or 6 digits: MCC + MNC)
networkRegistrationInfo	Detailed network registration information including domain, network type, and registration state
slot	SIM slot number. Numbering does not start at 0 or 1, and can be any arbitrary number
nonTerrestrialNetwork	true if the current network connection is operating over a Non-Terrestrial Network (e.g., satellite)

Device status

Device battery and location source information.

The gnss* and network* columns (and gnssAge and networkAge) are only filled when Location source in Settings is set to All. See Location provider.

File pattern: craxiom-devicestatus-YYYYMMDD-HHMMSS.csv CSV Version: 0.6.0 Columns: 22

deviceTime,latitude,longitude,altitude,speed,accuracy,batteryLevelPercent,gnssLatitude,gnssLongitude,gnssAltitude,gnssAccuracy,networkLatitude,networkLongitude,networkAltitude,networkAccuracy,deviceSerialNumber,locationAge,missionId,recordNumber,gnssAge,networkAge,mockLocation

Field	Description
(common)	Common fields also apply (note: Device Status does not use groupNumber): deviceTime, latitude, longitude, altitude, etc.
batteryLevelPercent	Battery charge level as percentage (0-100)
gnssLatitude	Latitude from GNSS provider, for comparison and analysis purposes
gnssLongitude	Longitude from GNSS provider, for comparison and analysis purposes
gnssAltitude	Altitude from GNSS provider in meters, for comparison and analysis purposes
gnssAccuracy	GNSS location accuracy in meters, for comparison and analysis purposes
networkLatitude	Latitude from network provider (e.g., Cellular and/or Wi-Fi), for comparison and analysis purposes
networkLongitude	Longitude from network provider (e.g., Cellular and/or Wi-Fi), for comparison and analysis purposes
networkAltitude	Altitude from network provider in meters (e.g., Cellular and/or Wi-Fi), for comparison and analysis purposes
networkAccuracy	Network location accuracy in meters (e.g., Cellular and/or Wi-Fi), for comparison and analysis purposes
gnssAge	Age in milliseconds of the GNSS provider fix reported in gnssLatitude/gnssLongitude. Empty means the age is unknown. A growing age against an unchanging position is a receiver that has stopped producing fixes
networkAge	Age in milliseconds of the network provider fix reported in networkLatitude/networkLongitude. Empty means the age is unknown
mockLocation	true when the primary location came from a mock location provider. Only ever written as true; an empty cell means the location was not mocked

CDR

The Call records file: calls, SMS and MMS messages (CDR build only), and LAC/TAC changes. See Call records for what each event means.

File pattern: craxiom-cdr-YYYYMMDD-HHMMSS.csv CSV Version: 0.5.0 Columns: 17

startTime,latitude,longitude,altitude,accuracy,event,originatingAddress,destinationAddress,csAccessNetworkTechnology,csCellIdentifier,psAccessNetworkTechnology,psCellIdentifier,slot,locationAge,deviceSerialNumber,missionId,recordNumber

Field	Description
startTime	Event timestamp as RFC3339 date-time with timezone
event	Event type: INCOMING_CALL, OUTGOING_CALL, INCOMING_SMS, OUTGOING_SMS, INCOMING_MMS, OUTGOING_MMS, or LOCATION_UPDATE
originatingAddress	Sender phone number or address. Empty on LOCATION_UPDATE. See the note below for which numbers each build can fill in
destinationAddress	Recipient phone number(s) or address(es). An outgoing group MMS lists every recipient separated by ;. Empty on LOCATION_UPDATE
csAccessNetworkTechnology	Circuit-switched network technology (e.g., LTE, UMTS)
csCellIdentifier	Circuit-switched cell identifier
psAccessNetworkTechnology	Packet-switched network technology
psCellIdentifier	Packet-switched cell identifier
slot	SIM slot number. As in the cellular files, numbering does not start at 0 or 1 and can be any number

Phone numbers in call records

This phone’s own number is written when the optional Read phone numbers permission is granted, in both builds: as originatingAddress on an outgoing call and as destinationAddress on an incoming call. The other party’s number needs the call log permission, which only the CDR build asks for. Without these permissions the cells are empty.

---

Related

• Log files: where the files are, sharing them, and when a new file starts
• Call records: what each call record event means
• Cellular networks: understanding cellular fields
• NS Messaging API: complete field specifications and enum values