Loading the evidence…
Preparing your view.
Preparing your view.

Armoured vehiclesIn service
Katmerciler Hızır is documented in current military inventories originating in Turkey. It was built by Katmerciler. Current inventory lists document it in Kenya.
Turkey
Turkish Armed Forces
Katmerciler Aselsan
Katmerciler
16.000 kg (both versions)
5570 mm (Hızır), 6000 mm (Ateş)
2490 mm (Hızır), 2500 mm (Ateş)
2610 mm (Hızır), 2600 mm (Ateş)
2 (commander, driver)
7 (Hızır), 4 (Ateş)
STANAG 4569 Level 2
(optional) 7.62 mm caliber medium machine gun, or 12.7mm caliber heavy machine gun or 40 mm caliber grenade launcher (all operated from inside the vehicle through a remote-controlled system designed by Aselsan)
Cummins ISL 8.9-liter, inline-six cylinder, turbocharged, intercooled diesel 400 PS (298 kW) @ 2100 rpm
six-speed, fully automatic Allison 3000 Series
fully independent with coil springs and shock absorbers
410 mm
700 km (435 miles) at cruising speed
120 km/h
power-assisted, front axle
Turkey : 57 Hızır 4x4 Ateş border patrol variants operated by Turkish Land Forces
Uruguay : 1 Hızır 4x4 Ateş procured in October 2021 to be used by the Uruguay Mechanized Infantry Unit under the United Nations Disengagement Observer Force mission.
Gambia : 20 Hızır 4x4 MRAPs ordered to be operated by Gambia Armed Forces . Deliveries began in October 2022, with first few examples already accepted into service. Besides the 20 purchased vehicles the Turkish government donated 2 additional Hızır MRAPs to the Gambian Armed Forces in November 2022.
Rwanda : Both Hızır MRAP and Ateş border patrol variants on order to be operated by Rwanda Defence Force .
Senegal : Hızır II variant in use, deliveries started in 2024.
Reference text from Wikipedia contributors, used under CC BY-SA 4.0.
Katmerciler Hızır equipment records. Variants, orders and quantities are shown as reported in each inventory source; coverage is incomplete.
Reported count for Katmerciler Hızır. Service scope: Kenya Army; does not replace a national total. 1 distinct count cell(s) from the same source list; shared rowspan cells counted once. Retired, wholly reserve and on-order rows are excluded; the reported count retains any explicitly mixed stock scope in the quoted row. Count column(s): quantity: 118. Origin: Turkey. The listed variants/roles are the scope, not an immediately deployable count. Dates are the count-cell citations' stated source period (2020), not the article revision. Cited source 2020-08-11. Edition or publication years do not claim an exact inventory census day.
Gambian National Army exact named equipment holdings: Hizir. Active, operational-reserve and training units excluding equipment in store; November 2025 IISS assessment. Named service only; no parent-force or national total inferred. Source role: ARMOURED FIGHTING VEHICLES / PPV. Original estimates, ranges, reporting names, reserve, lease and employment scopes retained; nested included counts are not added. Missile-system quantities mean launchers, not rounds. No readiness, crew, carried weapon, payload, factory-production or future order count inherited.
Ugandan People’s Defence Force exact named equipment holdings: Hizir. Active, operational-reserve and training units excluding equipment in store; November 2025 IISS assessment. Named service only; no parent-force or national total inferred. Source role: ARMOURED FIGHTING VEHICLES / PPV. Original estimates, ranges, reporting names, reserve, lease and employment scopes retained; nested included counts are not added. Missile-system quantities mean launchers, not rounds. No readiness, crew, carried weapon, payload, factory-production or future order count inherited.
Reported count for Katmerciler Hızır. Service scope: Uruguayan Army; does not replace a national total. 1 distinct count cell(s) from the same source list; shared rowspan cells counted once. Retired, wholly reserve and on-order rows are excluded; the reported count retains any explicitly mixed stock scope in the quoted row. Count column(s): quantity: 1. Origin: Turkey. The listed variants/roles are the scope, not an immediately deployable count. The components do not establish one inventory census date; the stored date is the retrieved source snapshot.