Skip to content
Company vehicle in Cyprus.

GPS Tracking in Cyprus: The Complete Guide

A practical guide to choosing, installing and using vehicle tracking across Cyprus, with clear limits on what the records can tell you.

Start with the decision you need to make

A tracking project starts with a business question, not a box under the dashboard. Dispatch may need the latest vehicle position to allocate a nearby van. A transport manager may need yesterday’s trip and stops to answer a delivery query. A finance team may need fuel entries matched to the right vehicle. A site manager may need to know which team is due at a job. Write those decisions down before comparing hardware. The relevant data, reporting interval, access rights and retention can differ for each one. If a purpose does not require a continuous route, do not collect one simply because a tracker can produce it.

Think about the record as three layers. The device estimates a position and records events; a mobile connection carries reports; a server receives them and presents a usable history. A live map is the latest report available, not a promise that the vehicle is at that point at this instant. A stop is evidence that a vehicle remained in an area according to its reports, not proof of what a person did there. An ignition event is about the vehicle, not a clock-in. Keeping those distinctions visible helps you buy the right system and prevents bad operational or employment decisions.

How a position becomes a fleet record

A vehicle tracker records a satellite-navigation position and time, then sends its own report over a mobile data connection to the receiving service. Fleet reads timestamps, coordinates, speed, heading, satellite count and device inputs from Teltonika reports. The server must decide which reports have a valid position, place them in time order and protect them from the wrong user. A map then turns those records into a current status or a route. These stages explain why “GPS” alone is a poor purchasing description: satellite reception, mobile coverage, server ingestion and the user’s permissions all matter.

Separate a GPS fix from a mobile connection. A device can be connected yet have no reliable position, for example when satellite signals are obstructed. It may also hold recorded positions while mobile data is unavailable, then send them later. The fleet view should show the report time and the quality of the fix rather than silently present an old point as current. The Fleet card shows last-report and GPS-fix indicators, Fleet accepts later batches of stored reports, and a report without satellites is marked as having no fix. This is a useful way to evaluate a demonstration: ask the supplier to show a no-fix state and an overdue report, not only a moving vehicle on a good day.

Choose the events that serve the purpose

A small van fleet often needs a live location, trips, stop times and a route replay. Fuel is a separate record: litres, spend and the vehicle or driver to which an entry belongs. The unit installed here does not report a fuel level through CAN or OBD; a fuel graph built from entered or imported transactions is a different thing from a tank sensor. Driving alerts also need careful labels. A harsh-braking or speeding event can prompt a review, but an event is not a reliable personal score or proof of fault. Ask exactly which device input produces each event, whether the scenario is enabled during installation and what a manager can inspect before acting.

For attendance, keep the clock-in record distinct from the vehicle record. A vehicle stop does not establish paid time, and a journey does not clock a person in. The useful link is contextual: when a driver is identified for a vehicle, a manager can compare Fleet trip history with staff hours recorded elsewhere in the same product. The records remain separate, so GPS is not treated as a payroll clock. This also changes access design. Someone handling dispatch may need the live map; payroll staff may need approved hours; neither role automatically needs every field in the other view.

Choose the tracker before choosing the dashboard

A wired tracker draws vehicle power and can use ignition or other installed inputs, making it suitable for a van that reports during each working day. A battery device may suit an item with no accessible vehicle supply, but charging, battery life and reporting frequency become central buying questions. Ask for the installation drawing, what happens when external power is removed and who maintains the device. An internal backup battery is not the same as an independent, long-life asset tracker. Do not assume the same unit is right for a generator, a trailer and a delivery van.

Compare electrical and mechanical fit. Check the vehicle supply range, fuse and mounting location, antenna exposure, enclosure rating, service access and whether the installation is reversible. The FTC164 has no CAN or OBD interface. A proposal to read vehicle CAN data therefore requires different equipment and a separate demonstration of how that data reaches the software. A device having an input or a published feature does not mean the service has a screen, storage and a calculation for it. The FTC164 does not report a fuel level. That distinction avoids an expensive promise based on a hardware brochure.

SIM data and coverage in Cyprus

The tracker needs a working mobile data path to make a new report visible to the office. Review the intended network coverage on the actual routes, including depots, underground parking and rural work sites, rather than relying on a country-wide colour map. Record the SIM provider, APN, roaming policy, data allowance, renewal arrangement and who receives a failure notice. A data allowance is only meaningful alongside reporting frequency and actual transmitted volume. If devices are bought separately from the software, confirm who owns the SIM and who diagnoses a silent device.

Roaming can affect how a device registers on a network, but do not infer that any particular SIM will attach to every network at every site. Test in vehicles and locations that matter. Ask the supplier to show the difference between a tracker that is offline, one that is connected without a GPS fix and one that is catching up with stored reports. The Fleet interface has separate states for these cases. This is more useful than a generic “coverage across Cyprus” statement when a manager must decide whether a van is still at the displayed point.

Plan installation across the five service districts

For work in Nicosia, Limassol, Larnaca, Paphos and Famagusta, make a vehicle list before booking installations. Record plate, type, home location, usual driver if one exists, power arrangement and any operational constraint such as a refrigerated vehicle or a leased van. Ask who approves the mount point and whether the vehicle needs to be available outside delivery hours. An installation appointment is also the moment to confirm the SIM, device identity and reporting configuration against the vehicle record. A tracker accidentally assigned to the wrong plate can make every later route look plausible and still be wrong.

The acceptance check should use a real trip. Confirm a current fix with a visible timestamp, then check that ignition, stop and power-off are represented as expected. Test a place with weaker reception and confirm that an older report is marked as older. Check that users assigned to a location can see the appropriate vehicle and a user outside that scope cannot. If private use is part of the policy, test the installed private-mode control and verify that a private trip has distance but no position. Keep an installation record for the device and vehicle pairing. This process matters more than the number of pins on a specification sheet.

Budget for the whole service, not one box

A useful quote separates hardware, installation, SIM data, software access, maintenance, replacement and support. Ask whether the device is bought or leased, who owns it, and what happens when a vehicle is sold or the tracker moves. Ask whether the mobile connection is part of the price and whether roaming or renewal changes it. Request a written explanation of the reporting interval and of any fair-use limit. A low entry price can hide a later installation charge; a high box price can be reasonable if it includes service work you would otherwise buy separately. Compare the same scope on each quotation.

Specify the roles and vehicles included in the quote. A team may need dispatch users, alert recipients and staff who review fuel entries; those are different activities. Ask how many vehicles are active at once, how old routes can be opened, what a replacement unit costs and how a fault is handled. Do not infer a price from a generic tracker advertisement. This site does not publish an unsupported fleet price: request a quote tied to your vehicle count and installation requirements.

Employee location data needs a documented purpose

A named driver’s route can be personal data. In Cyprus, the GDPR applies alongside Law 125(I)/2018, and the Commissioner for Personal Data Protection is the national supervisory authority. The local Commissioner’s published opinion on biometric attendance shows the importance of necessity and proportionality, while the European workplace-monitoring opinion (WP249, non-binding guidance) recommends assessing monitoring before deployment. European data protection guidance treats systematic monitoring of employees, such as tracking the vehicles they drive, as processing that usually needs a data protection impact assessment (DPIA). Before you roll out tracking, check whether one is required; for employee tracking it usually is. Those sources are linked below. They do not create a blanket approval for vehicle tracking. Write down the specific operational purpose, why the chosen level of location detail is necessary and who can access it. Consult the people responsible for your employment and data-protection decisions before switching tracking on.

Give drivers a plain notice before use. It should explain which vehicles and trips are covered, the data recorded, the purposes, who can open live and historic positions, retention, how a person can raise a concern, and what happens outside work. If a worker body or representative process applies to your organisation, handle that process as part of the rollout; do not present it as a universal Cyprus legal requirement without checking. Private mode is one technical control, not a substitute for purpose, transparency or access control. In this product a private trip keeps distance and duration but removes its position; the policy must still say when and how that mode is used.

Sources: [1][2][3][5][8][9]

Understand missing positions without inventing a cause

A gap in the map does not diagnose its own cause. Satellite reception may be unavailable, a mobile connection may be interrupted, power may be lost or the tracker may be configured to report less often. Interference is another possible explanation, but a single missing fix is not evidence of jamming. The appropriate first response is to inspect the last report, fix quality, power state and later records. Fleet treats a report with zero satellites as having no fix, even when coordinates repeat the last known position. Fleet can show a no-fix state rather than treating that repeated coordinate as fresh proof of location.

Where mobile delivery is delayed, later batches can appear after connectivity returns. A reconstructed route should use each report’s own time; a late arrival to the server is not a live point. Do not promise that every lost fix is recoverable, that every delayed message will arrive, or that the system can establish whether a deliberate jammer was used. A purchasing demonstration should include a disconnected device and a recovered batch so that dispatch staff know what uncertainty looks like. The aviation evidence below does not establish the frequency or location of road-vehicle interference in Cyprus.

Put vehicle activity beside staff hours without mixing them

Fleet and attendance being in one product is useful because it removes a manual matching task. The driver can be linked to the vehicle, while the attendance module records their clock-in and approved hours. The manager can inspect the vehicle’s trips and stops in their own context, then inspect work hours in the attendance context. A route may help explain why a team arrived after a shift began, but it does not itself change a timesheet. A stop at a customer does not prove a person worked for the entire stop, and travel between places does not automatically become payable time. Those decisions follow employment records and policy, not GPS dots.

Design a review workflow around exceptions rather than minute-by-minute surveillance. If a vehicle was used outside an expected window, check the schedule, driver assignment and any authorised private use before taking action. If the driver carried an iButton key, that may identify the driver for a trip; a usual-driver field is a different level of evidence. If fuel spend looks unusual, review the transaction and vehicle usage before treating it as misconduct. The combined view helps ask better questions, but the primary records and their limits must stay visible.

Compare approaches on the same questions

A phone location app, a wired vehicle tracker and a battery device answer different questions. A phone follows the person and depends on phone power, permissions and the app being active. A wired tracker follows the vehicle and can work with fitted inputs. A battery device can suit an asset that has no vehicle supply but trades reporting frequency against maintenance. Do not collapse these into one price per unit. Compare what each records, who it follows, what powers it, whether private use is possible and what happens during lost reception. The table below is a starting point for a supplier discussion, not a claim about any named competitor.

A buyer checklist to take into a demonstration

Bring a list of vehicle types, districts, typical routes, drivers, existing fuel-card sources and the decisions the office needs to make. Ask to see a current vehicle, an older trip, a stop with its duration, a private trip, an overdue report and a no-fix state. Ask who can see each example and to show a manager outside the vehicle’s location scope. Request the exact device model, power wiring, SIM arrangement, reporting settings and installation acceptance procedure. Ask which alerts come from the tracker and which are calculated on the server; request a live example rather than a brochure list.

Before signing, record the scope of the quote, ownership of devices and data, support hours, replacement process, export arrangements and retention policy. Have the privacy notice and access matrix reviewed by the people responsible for staff data. Pilot a small number of different vehicles, not only the easiest van in the depot. Include a route where connectivity is weaker and a driver who uses the vehicle privately if your policy permits that. The goal of the pilot is to expose operational limits early enough to decide whether the system fits.

Learn to read a route as evidence

A route is a sequence of recorded positions, not a continuous film. Between two reports the vehicle may have taken a different street, stopped briefly or entered a covered area. The distance and driving time shown by Fleet are the system’s trip values, which should be read with the time window and any missing fixes. When checking a complaint, open the relevant day rather than looking only at today’s marker. Record the plate, the report times, the driver identification method and any gap before drawing a conclusion. If the question is whether a delivery happened, pair the vehicle route with the delivery record; a marker near a customer does not establish handover.

The difference between a device timestamp and the time a report reaches the server is especially important after poor coverage. A batch that arrives at noon can describe movement at nine. Do not dispatch from its final point without checking the age of that point. In the Fleet interface, the overdue and catching-up states are designed to make that distinction visible. Train managers to say “last reported at” rather than “is at” whenever the data is old. That small change in language prevents operational errors and makes a later review more accurate.

Use zones for a place-based question

A zone can answer whether a vehicle entered or left a registered place. Fleet links its zones to sites and check-in places used by the attendance product, and rules can be set for entry or exit. That can help a supervisor notice a van arriving at a depot or site. A zone is not the same as proof that someone performed work there. The satellite fix, report interval and zone boundary all influence the event. A vehicle that drives along the edge may generate a result that deserves human review. Before using a zone alert for a serious decision, make a test trip into and out of the place and inspect the resulting timestamps.

Choose zone names the team recognises and assign an owner to each one. If a site moves or closes, update the source place rather than leaving a stale zone to generate alerts. Decide whether the office needs every entry or only exceptions outside planned hours. An alert without a response rule can become noise. For a construction site, ask the supervisor what action follows an arrival message. For a delivery depot, ask whether the dispatcher needs a zone event at all when the live map already answers the question. Minimise monitoring where a less detailed view works.

Design alerts around decisions and response times

The alert catalogue is broad: speeding, harsh movement, possible crash, towing, unplugging, battery conditions, long idle, after-hours movement, zone crossing and a report that has not arrived for the configured hours. A broad catalogue should not become a broad default. Start with the incidents the business can respond to. For each rule, name the vehicles, threshold, recipients, channel, quiet-hours policy and the person who closes the event. Check whether the event comes from a scenario that must be enabled on the tracker at installation. A server rule cannot recreate a device event that the device never sent.

Review alert quality after the pilot. Count which alerts led to a useful action, which were caused by installation or data issues and which lacked enough context. Where a false alarm could cause a serious accusation, require a second review of the underlying trip. In private mode, the alert should not expose a position that the route does not contain. Keep the distinction between possible crash, possible towing and a confirmed incident in every notification and conversation. The point of an alert is to direct attention promptly, not to replace the judgement of a person who can inspect the situation.

Separate consumption, spend and estimates

Fuel spend is the sum of transactions assigned to a period and vehicle. Consumption relates litres to distance when both records cover a comparable period. Cost per kilometre combines spend and vehicle movement. Idle fuel is an estimate from idling hours and a vehicle-specific litres-per-hour setting. These figures are easy to put side by side and easy to confuse. A card statement may arrive later than the trip data, and a driver may fill near a period boundary. If a number looks improbable, inspect the source rows and date range before treating it as a vehicle fault or misuse.

The Fleet fuel workflow can import a statement, preview its mapping and show errors and duplicate candidates. That supports a review, not automatic correction of a client’s financial record. The FTC164 data path does not supply tank level, so neither an empty-tank warning nor a precise fuel theft calculation should be inferred from the map. Ask a vendor to demonstrate the provenance of one number: open the original transaction, its assigned plate and the route context. A buyer who can trace one value is better prepared than a buyer shown an impressive but unexplained dashboard.

Run a pilot that can fail honestly

Pick vehicles that represent the work, not only the easiest installation. Include a city delivery van with frequent stops, a vehicle that spends time at remote sites and a vehicle with approved private use if that is in scope. Record the question each pilot vehicle is meant to answer. Check a normal trip, a stop, an older report, a zone crossing and the driver assignment. Walk through an interruption and a private trip with the people who will use the system. Write down where the data is uncertain. A successful pilot is one that exposes limits before the organisation relies on the records.

Set pass criteria before looking at the result. For example: the device is paired with the correct plate; a manager in the right department sees the vehicle; one outside the scope does not; an outdated point is labelled with its age; a private trip contains no position; and a fuel import shows an unmatched plate rather than guessing. If a criterion fails, correct the cause and repeat the check. Do not silently edit source data to make a demo look clean. After the pilot, request a final scope and quote in writing, including devices, installation, SIM arrangements, software roles, support and how the system will be reviewed after rollout.

Questions for a supplier meeting

Ask to see the exact product that would be delivered. Which tracker model and firmware is fitted? Which input detects ignition, which events are enabled on the device, and how is private mode configured? Who supplies the SIM and what networks and roaming conditions apply to that contract? What happens if the SIM stops working? Can the supplier show the first report after a connection gap, including its original timestamp? How is a tracker moved to a replacement vehicle without moving the old vehicle’s history? These are practical acceptance questions, not requests for a glossy list of possibilities.

Ask equally precise questions about people and data. Who can see a live position, who can see historic routes, and who can change alert rules? Can a user from another department open this vehicle? What evidence is kept when someone views a position? How does the product handle a private trip? What is the export and deletion process at the end of the contract? Who drafts the employee notice and decides retention? A vendor should be able to demonstrate controls and explain their scope. If a requested capability is on a roadmap, keep it outside the purchase decision until it exists and has been tested.

Decide who owns each part of the rollout

The fleet owner should maintain the vehicle list, device assignment and the operational questions the map must answer. The installer should document wiring, power, the SIM fitted and the test trip. The person responsible for staff data should review purpose, notice, private use, permissions and retention. The dispatcher should accept the status display after seeing a current point, an overdue report and a no-fix state. Finance should accept a fuel import with a duplicate and an unmatched plate. If one person is expected to do all of this, give them time and a written checklist. A project can fail when every individual component works but nobody owns the handoff between them.

Record a named route for support. When a vehicle disappears from the map, the office should know whether to call the driver, installer, SIM provider or software support and what evidence to collect before doing so. The last report time, power state, GPS-fix status and whether other vehicles are affected are useful facts. A generic “GPS is broken” ticket is less useful. At renewal, review whether the vehicle count, routes, privacy policy and data allowance still match the contract. A tracker moved between vehicles needs a fresh acceptance check; an old installation form cannot prove the new one. These routine records are part of the cost of reliable tracking.

Finally, decide what success means after the first month. Ask dispatch whether the current positions were fresh enough for assignments. Ask the alert recipients whether the rules prompted action or only noise. Ask finance whether every displayed fuel figure could be traced to a transaction and a vehicle. Ask drivers whether the private-use explanation matched what they saw. If the answer is no, change the process or configuration and test again. Do not hide failures behind a long list of features. The aim is a service whose evidence can be understood at the moment a real decision is made.

A procurement document should define the boundary of the service. List the vehicles, the device fitted to each type, the SIM contract, the reporting configuration, the included user roles and the data the software will actually display. Keep separately any optional device capabilities that are not part of the delivered workflow. This makes a comparison of quotations meaningful and prevents a later disagreement about whether a hardware feature was also a software promise.

A privacy review should be equally concrete. Use a sample driver and vehicle to show what happens on a public trip, a private trip and a shift change. Check what the dispatcher, branch manager and payroll user can each open. Compare the screens with the employee notice and correct whichever side is inaccurate before the system goes live. Revisit the same examples after a tracker replacement or change in working pattern.

An evidence policy should say what to do when records disagree. If the GPS trail shows a stop but the delivery record has no completed job, the answer is to investigate the job, not to invent completion. If a card transaction appears for a vehicle that was elsewhere, inspect the card and assignment before accusing a driver. If the map has a gap, mark the interval unknown. This discipline gives the team useful answers without making the technology claim more certainty than it has.

The final choice should fit the organisation’s work, not the longest feature list. A small team may value clear timestamps and a reliable support contact more than many alerts. A larger fleet may need stronger assignment and permission routines. In either case, choose a pilot with a real interruption and a real exception, verify the response, then expand only when the people who will use the records can explain their meaning. Ask the office to describe what it would do with an old point, an unmatched fuel entry and a private trip. Its answers reveal whether training and policy are ready. That is how a GPS installation becomes a dependable part of daily operations.

Why a detailed trail can still be two minutes old

The FTC164 saves a record when a configured time, distance, turn or speed-change condition fires. Teltonika lists moving-home defaults of 100 metres, five minutes, a 10 degree turn and a 10 km/h speed change. These are device parameter defaults, not a confirmed setting on every unit we install. At 40 km/h, covering 100 metres takes about nine seconds. A moving van can therefore leave many points in its trail while the five-minute clock has not expired. The device checks whether to send its saved records on a separate schedule, listed as 120 seconds by default. The Fleet map updates after a report reaches our server; it cannot make an unsent record visible.

For dispatch, agree on the maximum acceptable report age, then test the actual device settings and coverage on a real route. Shorter send periods mean more network sessions and usually more energy use. Teltonika also documents on-demand fast tracking, but Fleet has no customer control to start it. Treat it as a device option to discuss, not a Fleet button. The server can push a received point to users quickly, yet that does not reduce the time the device held it before sending.

Estimate data and battery before selecting a send period

A rough Codec 8 Extended model with about a dozen input values puts one position record near 80 to 100 bytes before network overhead. Two hours of city driving a day at roughly one point per nine seconds gives about 800 records a day and around 3 MB a month for the records alone. A ten-second schedule running ten hours a day gives about 3,600 records a day and around 15 MB a month before network overhead. These are arithmetic estimates from the format and example driving patterns, not measured SIM usage. Session setup, retries, roaming and enabled inputs can change the bill. Use the SIM provider counter on the fitted unit for a real allowance.

Battery figures also depend on wake-ups. The FTC164 datasheet lists less than 26 mA in nominal use at 12 V, less than 9.71 mA in Online Deep Sleep and less than 0.28 mA in Power Off Sleep. At the 26 mA upper figure, arithmetic gives about 0.62 Ah a day from the vehicle. That is a planning estimate, not a prediction of when any car will fail to start: its battery condition and all other loads matter. Do not use the datasheet deep-sleep current as an exact mA figure because that row lacks a unit.

When the tracker looks offline, check four layers in order

First check the SIM and mobile network: account, data allowance, APN, roaming and whether several vehicles using the same service stopped together. Next check our edge: the last packet received, the tracker assignment and whether the map is showing a delayed batch or an overdue state. Then check vehicle power, backup battery and the configured sleep mode with the installer. Finally check the view of the sky and the reported fix. A device can have mobile service without a usable satellite fix, or a good recorded fix that has not yet reached the server. Fleet shows report age and a no-fix state, but it does not expose the FTC164 sleep-state, battery-percentage or radio-quality fields as a customer diagnostic.

Power Off Sleep is a particularly easy source of confusion: the device modem is off and it wakes on movement or its DIN1 input. Deep Sleep also switches off the modem until a wake condition. A last point in an underground car park is a clue, not a diagnosis. If one van is late, compare its last report with another on the same route and SIM arrangement. Escalate with timestamps and installation details before attributing a gap to interference or a person.

GPS interference in Cyprus: what the evidence covers

Cyprus aviation authorities have described GNSS interference affecting aviation in the Nicosia flight information region. The cited material does not establish how often road vehicles in Cyprus are affected, so a gap on a van route must not be labelled spoofing. Cellular jamming and GNSS interference are different: the FTC164 documents detection of cellular-network jamming, but its FTC164 input list does not document a GNSS-jamming or spoofing detector. Fleet does not currently turn the device cellular-jamming value into an alert.

If a received position has too few satellites or poor horizontal dilution, our derivation rejects it as a usable fix. The FTC164 may repeat its last valid coordinates when it has no new fix, which is why timestamp and fix status matter more than a marker alone. A failed fix filter can prevent a bad point being shown as current; it cannot prove why the radio environment changed. Keep aviation reports and ground-vehicle observations separate in any investigation.

Which work benefits, and where the current service stops

Delivery vans need timestamped stops, idling review and a useful dispatch age. The FTC164 can save dense distance and turn records; Fleet provides the live map, trips, zones, harsh-driving and long-idle alerts, and a fuel log built from entries and receipts. Field service needs time at each workplace; the tracker supplies trips and positions while Fleet derives zone visits and travel legs. Attendance remains a separate staff record.

Construction plant and agricultural machines may sit for days and face theft or wash-downs. The FTC164 has an IP69K enclosure, backup battery and scheduled reporting modes. Fleet currently provides positions, zones and after-hours, towing and unplug alerts when those device scenarios are configured. It has no engine-hours report and does not interpret implement input wires. Waste collection similarly needs route and idling review; the device can take a lift or tong switch on an input, while Fleet does not yet turn those input changes into a bin-lift record.

Rental fleets need overdue-return, crash and restricted-area review. The tracker can supply crash, tow, unplug and GNSS distance events; Fleet shows the corresponding alerts and zone history. A remote immobiliser is a device capability, not a Fleet control. Taxis need driver identity and driving events; Fleet supports iButton identification and harsh and speed alerts, but no taximeter integration. School buses need route and stop visibility; Fleet can show live position and zones, but has no parent-facing ETA.

Security patrols need evidence of visits, and Fleet has zone visits. Motorbike couriers need lift-theft review; the FTC164 has towing and fall-down scenarios, but Fleet only uses the towing and unplug events today. Trailers and containers benefit from the enclosure and long sleep endurance; Fleet has live status and zones, but no BLE door sensor view. Boats can use location and zones, subject to an installation and coverage check. Police and emergency fleets need availability; Fleet offers live position, without a response-time promise.

Cold-chain operators need temperature and door records. The FTC164 can work with BLE sensors and wired probes, but Fleet currently has no cold-chain screen or temperature alerts. Personal cars benefit from theft and privacy controls; Fleet offers position, configured alerts and private trips. Insurance programmes need auditable distance and scoring; the FTC164 has GNSS distance and driving events, while Fleet has no insurance score or approval claim. Company logbooks need a private/business split; Fleet can mask private positions while retaining distance. Each use needs the fitted configuration and a witnessed acceptance check.

Tracking approaches compared

QuestionWired vehicle trackerBattery or phone approach
What is followed?The fitted vehicleThe asset or the person carrying the device
PowerVehicle supply with the installed backup arrangementBattery charging and reporting interval need planning
Vehicle inputsPossible only where fitted, configured and supportedUsually unavailable without additional equipment
Private useRequires a clear policy and a tested controlRequires a clear policy and app or device control
Best first questionWhich vehicle decisions need a route?Which asset or person decision needs a position?

Sources

  1. Cyprus Law 125(I)/2018
  2. Cyprus DPC Opinion 2/2018
  3. Article 29 Working Party Opinion 2/2017
  4. GDPR Article 35
  5. GDPR Article 88
  6. GDPR Article 5
  7. GDPR Article 13
  8. Article 29 Working Party Guidelines on Data Protection Impact Assessment (WP248 rev.01)
  9. EDPB Opinion 10/2019 on the Cyprus draft list of processing operations subject to a DPIA
  10. Teltonika FTC164 datasheet
  11. Teltonika FTC164 tracking settings
  12. Teltonika Codec 8 Extended format
  13. Teltonika FTC164 parameter list
  14. Teltonika FTC164 system settings
  15. Teltonika FTC164 features
  16. Cyprus Department of Civil Aviation GNSS interference presentation
  17. Teltonika usage scenarios
  18. Teltonika FTC164 launch notes
  19. Teltonika FTC164 Bluetooth

Frequently asked questions

Does a live map always show the vehicle right now?

It shows the latest report available. Check its timestamp, connection and GPS-fix status before treating it as current.

Can a tracker tell us how many hours someone worked?

No. Trips and stops are vehicle records. Clock-ins and approved hours are attendance records, even when both are shown in one product.

Does the FTC164 measure fuel in the tank?

The FTC164 does not report fuel level. Fuel entries and imported card statements are separate records.

Does private mode erase the entire journey?

A private trip keeps distance and duration but stores no position or route in Fleet. The mode and its policy should be tested before rollout.

What should we do when a map point is old?

Check report time, GPS fix, power and connection state. Do not infer that the vehicle is still at the last point or that a jammer was involved.

How do we get a price?

Request a quote that names the vehicles, installation, SIM data, software access and support included in the scope.

Discuss your fleet requirements

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