Login
Compliance · Free Excel log

WASL message test log from the device

A free test log for the last step before a vehicle goes live on WASL in Saudi Arabia: trigger each event on the device, time it to your platform, and check every field arrived. It makes no approval claim, and it invents no field names.

Get the Excel log (.xlsx)Arabic version
Free: enter your name and e-mail and we email you the file. Works in Excel, Google Sheets and LibreOffice.
  • Device, platform, WASL
  • Clock offset handled
  • No official field names invented
How the test works

Three checkpoints from the device to WASL

The device reports to your tracking platform, and the platform forwards to WASL. A field lost at any step is lost for good, so the log checks the whole chain.

Deviceevent and timeYour platformtime receivedWASLif visible to you123DelayFields
Fig. 1 The log checks the chain at three points. Point 3 is optional: not every operator can see the WASL side.
tracom-wasl-message-test-log-en.xlsx
Data item (generic)Example from the deviceField name in your documentSource and versionFlag
Device ID or IMEI350000000000011Enter from your spec
Date and time of the position2026-11-04 06:00:05Enter from your spec
Speed42 km/hEnter from your spec
Ignition statusONEnter from your spec
The field names stay empty until you copy them from your current integration document. The flag says so until you do.
What's inside

What's in the WASL message test log?

Five working sheets and a list sheet. One log per vehicle.

  1. 01

    Setup

    Vehicle, IMEI, device, platform, activity, tester, the clock offset in hours and a summary with one log result.

  2. 02

    Field map

    14 generic data items with an example device value. You add the WASL field name, the source document, its version and the date you checked it.

  3. 03

    Test log

    8 events from ignition on to a device restart: device time, platform time, delay, fields arrived, values and a result.

  4. 04

    Sources

    Where each requirement comes from, the last-checked date and a Verify action for each.

Why test messages before go-live?

WASL is the electronic platform of the Transport General Authority (TGA) for land transport in Saudi Arabia. A vehicle can show on your tracking map and still send WASL an incomplete message: a missing heading, a time in the wrong zone, a speed in the wrong unit. You find out when the data is questioned. A one-hour test per vehicle type finds it first.

No approval, no official field names

This log is a test record made by the operator or the installer. A full pass does not mean the TGA, WASL or anyone else accepts the device, the platform or the operator. The file does not list official field names: copy them from your current integration document and verify against the current official text on tga.gov.sa.

Clocks and delay

Many trackers keep time in UTC, and many platforms show local time. Riyadh is UTC+3. Enter the hours between the two clocks once on the Setup sheet, and the log converts every device time before it works out the delay.

Delay (s) = (platform time − device time − hours ÷ 24) × 86,400 A delay below 0 means the clocks disagree: check the hours Result = Fail if no field arrived, Check if some fields are missing, a value differs or the delay is above your maximum, otherwise PassExample: device 06:00:00 UTC, platform 09:00:12 Riyadh time, 3 hours: delay 12 s.

The maximum delay for each event is your own target, not an official limit. Messages stored during a coverage loss arrive late by design, so that event has a longer example maximum. What matters there is that every stored position arrives with its original time.

The eight test events

  • Ignition on. Switch the ignition on with the vehicle parked.
  • Position while moving. Drive inside the yard for 5 min. Pick one periodic report.
  • Speed change. Hold a steady yard speed, then slow down. Compare the speed values.
  • Stop with the engine on. Stop and wait 3 min with the engine on.
  • Ignition off and park. Switch the ignition off.
  • Position while parked. Leave the vehicle parked through one parked report interval.
  • Coverage loss and recovery. Park where coverage is poor for 10 min, then drive out.
  • Device restart. Power the device off and on, with the ignition off.

Limits

The log records what you saw on one day for one vehicle. It does not replace the steps the TGA or your platform provider asks for, and it does not list or interpret their requirements. Check the TGA site for the current rules and for the tracking providers it recognizes.

Related Tracom solution

Know what your device sends

Tracom designs its trackers to time-stamp each event on the device. Which data items your model sends, in which time basis, and how many positions it keeps when coverage drops depend on the model, the firmware and the configuration. Ask us before you link a fleet.

  • Approval check tool to check a device or provider on the regulator list yourself.
  • Frame decoder to read the raw message the device sent.
  • SIM and APN setup sheet to confirm the device reaches the right server.
  • Alert test script to test the alerts in the same visit.
Questions

WASL message test questions, answered

Linking a fleet? Talk to Tracom.

Does the device send data to WASL directly?

Not usually. The device reports to a tracking platform, and the platform forwards to WASL. That is why the log times the device and the platform, and asks whether you can see the WASL side.

Why are the WASL field names empty?

Because they come from your current integration document, not from us. Copy them with the source and the version, and the flag clears. That keeps the file honest when the specification changes.

What maximum delay should I use?

Your own target, or the one in your integration document. The file uses 60 to 900 s as examples. They are not official limits.

Does a full pass mean the vehicle is approved?

No. It means the events you tested reached your platform with all their fields on that day. Linking and acceptance follow the TGA process and your platform provider.

What does Tracom do beyond the template?

Tracom makes the devices and can tell you which events and data items your model sends. Tracom does not link vehicles to WASL, and the log makes no claim that any device, platform or operator is approved.

Next step

Preparing a fleet for WASL?

Tell us the device models. We will tell you which data items they send.

Contact Us Get the log
Related tools and templates

More for device data and compliance

TechnicalTemplate

SIM / APN and server setup sheet

Device not connecting after install? Keep the APN and server values in one sheet and log five checks per activation.

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Tracom uses your details to send what you requested and may contact you about it. See our privacy notice for your rights and how to delete your data.

Tracom is an advanced GPS tracking device designed to enhance fleet visibility, safety, and efficiency through real-time data, intelligent alerts, and remote monitoring.

Device

Help

Facebook Youtube Linkedin Instagram X-twitter

Copyright © 2026 SAFEE

Scroll to Top