Skip to content
Company vehicle in Cyprus.

GPS tracker for vehicles in Cyprus

The device is one part of the service. Match its power, reporting and installation to the vehicle and the decisions you need to make.

Fit the tracker to a vehicle, not a product photo

A van can usually supply a wired device, but the right installation still depends on its electrical system, where it is parked, who maintains it and whether it is leased. Before buying, make a vehicle list with model, year, plate and the use of each vehicle. Ask the installer to identify a safe power source, fuse and location that protects the equipment while allowing service access. A device with a backup battery can keep operating after external power is removed, but that is not the same as a battery asset tracker intended to run for long periods without vehicle power. The installer should tell you what behaviour to expect from the exact fitted configuration.

Fleet reads position, timestamp, speed, heading and satellite count from Teltonika tracker records, and the FTC164 and its family are supported devices. That means Fleet can receive their reports; it is not a promise that every function printed in a hardware catalogue is enabled in a customer installation. Treat optional inputs and driver identification as separate acceptance items. The FTC164 has no CAN or OBD interface and does not report fuel level. If a seller describes “fuel monitoring,” ask whether they mean card transactions, manually reviewed entries or a separately installed sensor supported by the software.

Check the SIM and the age of every report

The SIM is the tracker’s path to the server. Check the APN, roaming policy, allowance, renewal date and responsibility for faults. The Fleet setup notes use a 1NCE APN as a configuration example; that does not mean every customer device uses a 1NCE SIM or that data is included in every contract. Ask what SIM will actually be fitted to your vehicles and have its details written into the installation record. Test the route and depot locations that matter to your business, especially covered parking and work sites where a generic coverage map says little about the installed device.

A receiver may lose a valid satellite fix while still sending data. The decoder marks a position with zero satellites as lacking a fix, even when the raw coordinates repeat a last known position. The Fleet interface has distinct states for no fix, offline and catching up with stored data. During a demonstration, ask the supplier to show each state and the report timestamp. An old point should never be presented to dispatch as a fresh arrival. Ask what the map does when reports arrive late, and whether the route is sorted by the device’s recorded time.

Make the installation test repeatable

At handover, match the device identifier to the right plate, then make a short trip with a known start, stop and finish. Check that the map shows a fix, that the trip and stop appear in the right order and that the last-report time moves. Remove external power only if the installer has a safe test procedure, and confirm that the expected status appears. If the installation includes a private-mode control, run a private trip and verify that the system stores distance without a route. Record the result and the person who accepted the fit. Repeat the same test when a tracker moves to another vehicle.

Ask about support before a unit goes silent. Who checks power and SIM first? Who can inspect the last report? What replaces a failed unit and how does the historic route remain tied to the vehicle? The Fleet catalogue keeps the tracker and vehicle relationship explicit, which matters when vehicles are replaced. An identifier assigned to the wrong vehicle can create a convincing but false history. A written acceptance record is a small control with a large effect.

Power and mounting questions for the installer

Before work begins, ask the installer to identify the intended power source, fuse and route for wiring. Record whether the vehicle has any existing electrical modifications that affect a safe mount. A fleet device should be reachable for service without inviting accidental unplugging in daily use. Check whether the vehicle is owned, leased or under a warranty condition that affects installation. These are decisions for a qualified installer and the vehicle owner, not a generic wiring instruction from a marketing page. The acceptance sheet should state where the unit is fitted and how an authorised person can inspect it.

Plan for power loss as an operational event. The tracker can report a power change and Fleet has an unplug alert kind, but an alert needs its rule and device scenario configured. Ask the installer to demonstrate the expected state safely. Decide who receives the alert, whether the first response is to call a driver or check the vehicle, and how a known maintenance disconnection is recorded. A backup battery gives some resilience; its practical runtime depends on the actual device and settings. Do not equate a backup cell with a guarantee of continuous reporting through every fault.

Treat each optional input as a separate project

A device may have physical inputs and an acceleration sensor, but useful software requires the right wiring, configuration, ingestion and display. Write an acceptance row for each requested input: what physical event creates it, what data the device sends, which screen shows it and who reviews it. The FTC164 does not report fuel level. A proposed CAN connection, temperature sensor or external switch therefore needs its own evidence. If a feature is not in the delivered Fleet screen, do not assume a data pin makes it available.

Driver identity deserves the same care. Fleet can use an iButton key to identify the driver and also has a usual-driver field for a vehicle. The two can disagree if the van is shared or a key was not used. An event attributed through the usual-driver field should be described as an assignment, not a confirmed person at the wheel. Test a shared vehicle during the pilot and decide what the office should display when identity is uncertain.

Diagnose a silent device in the right order

When a unit stops reporting, note the last received time first. Check whether other devices with the same SIM arrangement are affected, then inspect power and the device’s mobile connection according to the installer’s procedure. A no-fix state can still mean the mobile path is working; an offline state means no current report has reached the service. A later batch may fill the trail. Keep the original report times visible so the office does not mistake catch-up for a fresh position. Do not diagnose deliberate interference from a single gap.

The installation notes include an APN example for 1NCE. Use that as evidence of a supported configuration example, not a promise about the commercial SIM in every fitted unit. Ask the supplier for the actual SIM terms, renewal contact and a procedure for replacement. If the vehicle routinely parks under a roof, include that location in the handover test and agree what status the dispatcher should expect.

Make replacements and transfers auditable

A device can be removed from one van and placed in another. The vehicle catalogue must preserve the historical relationship so a route recorded before the transfer is not shown as belonging to the new plate. Record removal time, installation time, identifiers and the person authorising the change. Make a fresh test trip after reassignment. If a device is retired, leave the old vehicle history intact and stop new reports being attached to it. This is a data-quality control as well as an equipment control.

At handover, give the office a one-page guide to the states it will actually see: moving, parked, overdue, offline, no fix, catching up, unplugged and private. Include who to call for each condition. That guide is more useful than a long list of hardware capabilities that nobody has configured. Confirm that the first live record appears under the correct location and department scope, then let the dispatcher, not only the installer, accept the screen.

A device decision sheet

For each vehicle, put the plate and model beside the intended tracker, power source, mount location, SIM, driver-identification method and private-use control. Mark every optional input as requested, delivered or excluded. That last column matters: the FTC164 has an acceleration sensor and optional input wiring, but no CAN or OBD interface, and hardware alone does not deliver a Fleet screen. The sheet lets an installer and a buyer agree on the same outcome before anything is fitted. It also protects the fleet catalogue from a device identifier being assigned to the wrong van.

Add three observations from the acceptance drive. What did the current card show at departure? How long did the first trip take to appear? Did the last-report time and GPS-fix state make sense after parking? If private mode is included, run a separate trip and check that its position is absent while distance remains. If an unplug alert is included, have the installer demonstrate it safely and note whether the device-side scenario and Fleet rule were enabled. Do not accept “the hardware supports it” in place of an observed result.

Keep this sheet when the vehicle is sold. It tells the next reviewer which unit to remove, which SIM to cancel or transfer and what records belonged to the old installation. A replacement unit can then be assigned with a new start date. The historical trail remains associated with the vehicle that produced it. In a shared fleet, this discipline prevents a convincing but false route from being attributed to a different plate.

Choose sleep mode for the parked vehicle

Online Deep Sleep keeps the modem reachable while turning off satellite acquisition and several driving scenarios. It suits a vehicle that needs regular contact, provided the installer tests its wake and report timing. Deep Sleep turns the modem off and stores periodic records until it wakes, trading immediate visibility for less draw. Power Off Sleep uses the least power and wakes on accelerometer movement or DIN1, so it may suit a parked trailer or machine checked infrequently. These are the three FTC164 modes; their names and behaviour come from Teltonika system documentation.

Power Off Sleep disables towing and unplug detection. It is a poor choice when those alarms are the reason a car is being tracked. Deep Sleep and Power Off Sleep cannot receive the device commands while the modem is off. Teltonika describes up to 150 days on the internal battery with one daily report in Power Off Sleep; that is a vendor condition, not a promised runtime for a vehicle sending frequently. Our Fleet view does not show the device sleep-state field. Ask the installer to record the chosen mode and demonstrate the wake path.

Mount for Cyprus heat and a reliable fix

The FTC164 datasheet permits operation with its battery from minus 20 to plus 60 degrees Celsius, but charges that battery only from zero to plus 45 degrees Celsius. Direct sun on a dashboard can exceed those limits. A parked-car study in Arizona measured high cabin and dashboard temperatures; those figures are an illustration of the risk, not a Cyprus measurement. Place the unit low, away from direct sun and heat sources, and avoid a metal enclosure that blocks its internal satellite antenna. Keep the mount firm so acceleration events and calibration have a stable reference.

The Teltonika installation guide specifies a fused power feed, sound ground, insulated conductors and wiring secured away from moving or hot parts. Ask the installer to check the fuse and power supply for this vehicle and to photograph the final mount for service. A device installed where it overheats or loses sky view can create gaps that software cannot repair.

The tracker can also do more than Fleet uses today

The hardware has digital and analog inputs, four outputs, Bluetooth and 1-Wire. Teltonika documents input switches, BLE temperature and door sensors, a device immobiliser, cellular-jamming events, battery percentage, signal quality and remote configuration through its tools. Fleet does not currently present those input values as customer controls or cold-chain alerts. Bluetooth driver tags and RFID are likewise not part of Fleet driver identification; Fleet uses iButton today. Discuss any extra sensor, relay or driver key as an available-on-request installation with its own software acceptance criteria.

The FTC164 has no CAN or OBD connector. It cannot read actual tank level, engine RPM or fault codes from the vehicle. Fleet fuel records come from entered transactions, receipt photos where reading is enabled, and imported fuel-card files. The device has an estimated fuel-used counter based on distance and a configured rate, but Fleet does not use it as a tank measurement. Remote firmware updates exist through Teltonika FOTA WEB, not through a Fleet customer control. The same boundary applies to SMS and WhatsApp alerts: Fleet delivers alerts in the app, by push and by email.

Sources

  1. Teltonika FTC164 datasheet
  2. Teltonika FTC164 system settings
  3. Teltonika FTC164 first start and installation
  4. Arizona State University parked-car heat study
  5. Teltonika FTC164 Bluetooth
  6. Teltonika FTC164 command list
  7. Teltonika FOTA WEB
  8. Teltonika FTC164 launch notes

Frequently asked questions

Is a backup battery a long-life asset tracker?

No. It is backup power for the fitted vehicle device. Ask for the expected runtime and behaviour of the exact installation.

Can the FTC164 show tank level?

No. The FTC164 does not report fuel level. Confirm any separate sensor and software support before buying one.

What should we record at handover?

Device identifier, plate, power and SIM arrangement, reporting configuration, a test trip and the person who accepted the installation.

Discuss your fleet requirements

Ask for a quote based on your vehicles and operational needs.