# Japan Used Trucks (55truck.com) (`jpopendata/japan-used-trucks-55truck`) Actor

Japanese used commercial-vehicle listings from 55truck.com (トラック王国) — price, year, mileage, load capacity, body type, size, transmission and inspection by maker/body-type/size, English schema. Unofficial; not affiliated with 55truck / トラック王国.

- **URL**: https://apify.com/jpopendata/japan-used-trucks-55truck.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Japan Used Trucks (55truck.com)

**Japanese used commercial-vehicle listings — price, year, mileage, maximum load capacity, body type, size class, transmission and inspection status — from 55truck.com (トラック王国), one of Japan's largest used-truck marketplaces, in a clean English schema.**

This Actor searches 55truck.com's public used-truck listings by maker, body type and size class and returns each vehicle as English-schema JSON: maker (Japanese + English), model, body type (dump, crane, flatbed, refrigerated, wing, mixer, tractor head, forklift…), size class (小型 / 中型 / 増トン / 大型), vehicle price and total payment in JPY, first-registration year, mileage in km, **maximum load capacity (最大積載量) in kg**, transmission, emission-standard status, and 車検 (inspection) expiry or status. With `detailFetch` it adds the maker type code (型式), engine displacement, gross vehicle weight, fuel, engine model, seating, and the outer/cargo-bed dimensions from each vehicle's detail page. Optional client-side filters narrow by model keyword, price window (万円) and year window.

Japan is a major used-truck **export** source (dump trucks, cranes, refrigerated bodies and construction vehicles bound for Africa, Southeast Asia and beyond), but 55truck.com is Japanese-only — invisible to most international tooling. This Actor is the bridge.

> **Unofficial tool.** Not affiliated with or endorsed by 55truck / トラック王国 or its operator. It collects **publicly available data only** (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion), and extracts **factual data only** — vehicle facts and the seller's business identity (showroom region, inquiry reference number); no review content, no seller marketing prose, no personal data of any kind (relevant e.g. under GDPR: no personal data is collected or processed). Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

***

### Quick start — verified input

Copy, paste, run. This exact input is verified on the platform (SUCCEEDED, items > 0):

```json
{
  "maker": "Hino",
  "bodyType": "dump",
  "maxItems": 10
}
```

Running with **no input at all** also works (it sweeps the newest listings across all makers). All filters are optional; `maker`, `bodyType` and `size` are applied upstream, the rest client-side.

### Who is this for?

- **Used-truck & heavy-equipment exporters** — source dump trucks, cranes, refrigerated bodies, tractor heads and construction vehicles by maker, body type, size, price and load capacity; the load-capacity (最大積載量), size class and inspection status are exactly the fields export buyers check first.
- **Market & price analysis** — used commercial-vehicle price levels by maker, body type, year and mileage; a public-listing dataset for a segment closed auction data rarely surfaces cleanly.
- **Fleet & valuation tools** — feed live Japanese retail asking prices for trucks into pricing models.
- **Data teams** — a stable English schema over a Japanese-only source.

### Sample output (dataset item)

```json
{
  "vehicleName": "日野 レンジャー 深ダンプ（土砂禁ダンプ）",
  "maker": "日野",
  "makerEn": "Hino",
  "model": "レンジャー",
  "bodyType": "深ダンプ（土砂禁ダンプ）",
  "bodyTypeEn": "Dump",
  "size": "中型（4t）",
  "sizeEn": "Medium (4t class)",
  "typeCode": "PB-FC6JCFA",
  "priceJpy": 3360000,
  "totalPaymentJpy": 3620000,
  "year": 2004,
  "mileageKm": 281489,
  "loadCapacityKg": 3050,
  "grossWeightKg": 7955,
  "transmission": "MT",
  "displacementCc": 4720,
  "fuel": "軽油",
  "engineModel": "J05D",
  "seatingCapacity": 3,
  "emissionStandard": "適合",
  "inspectionUntil": null,
  "inspectionNote": "一時抹消",
  "bodyDimensionsCm": "長550 幅228 高266",
  "bedDimensionsCm": "(約)長339 幅206 高145",
  "location": null,
  "refNo": "339703",
  "url": "https://www.55truck.com/truck/70638.html",
  "detailFetched": true,
  "source": "トラック王国 (55truck.com)",
  "sourceUrl": "https://www.55truck.com/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-26T09:10:00Z"
}
```

### Input example

```json
{
  "maker": "Hino",
  "bodyType": "dump",
  "size": "big",
  "yearMin": 2015,
  "priceMax": 800,
  "maxItems": 50
}
```

All filters are optional (leave everything empty to sweep the whole inventory). `maker` (Isuzu, Hino, Mitsubishi Fuso, UD Trucks, Nissan, Toyota, Mazda, Daihatsu, Mercedes-Benz, Scania, Volvo, plus heavy-equipment makers Komatsu, Hitachi, Kobelco, Kubota, Yanmar, Kato, Tadano, Caterpillar and more — Japanese names and slugs work too), `bodyType` (any 55truck figure such as `dump`, `crane`, `flatbody`, `coldfreezing`, `alumiwing`, `mixer`, `trailerhead`, `forklift`) and `size` (`small`/`middle`/`plus`/`big`) are applied upstream via the site's static filter pages. `model`, `priceMin`/`priceMax` (万円 = 10,000 JPY units) and `yearMin`/`yearMax` filter client-side.

#### Common input mistakes

| Mistake | Correct |
|---------|---------|
| `"maker": "Mitsubishi"` / `"Fuso"` | `"Mitsubishi Fuso"` (both of those spellings are accepted aliases; unknown makers fail with the full list) |
| `"size": "large"` / `"10t"` | accepted — canonical values are `small` / `middle` / `plus` / `big` |
| `"bodyType": "Space Shuttle"` | a real body type: `dump`, `crane`, `flatbody`, `coldfreezing`, `alumiwing`, `mixer`, `trailerhead`, `forklift` … (the error message lists them) |
| `"priceMax": 8000000` (yen) | `800` — prices are in **万円** (10,000-yen units) |
| `"yearMin": 18` / `"H30"` | a 4-digit year: `2018` |
| `"detailFetch": true` with `"maxItems": 100` and the default `maxApiRequests` | raise `maxApiRequests` (one extra request per vehicle) or the run stops early with `complete: false` |

#### Empty results?

A run that finds nothing completes with 0 items and a warning in the log (not a failure). Typical causes: a maker × body type × size combination 55truck has no listing page for (e.g. `"maker": "Caterpillar"` with `"bodyType": "alumiwing"` — the site answers 404 and the Actor reports 0 vehicles), a `bodyType` figure slug that exists in the sitemap but is empty, or a `model` / price / year filter that discards everything fetched. Drop the narrowest filter and retry.

### Pricing

Pay per result — see the pricing tab. A maker × body-type query is typically hundreds to thousands of vehicles upstream; `maxItems` caps what you take.

### FAQ

**Where does the data come from?**
Live from 55truck.com's public, login-free static list and vehicle detail pages at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

**Is this an official 55truck / トラック王国 service?**
No. **Unofficial**, independently built and maintained, and **not affiliated with or endorsed by 55truck / トラック王国**. It reads only publicly available pages.

**Why is there no dealer / prefecture field?**
55truck is a single broker that stocks vehicles at its own regional showrooms — not a marketplace of independent dealers. The vehicle's showroom region is surfaced as `location` (often shown as "contact for details" upstream, in which case it is null). For passenger cars sold by independent dealers with prefecture addresses, see the companion Actor **Japan Used Cars (carsensor.net)**.

**Are reviews or seller marketing texts included?**
No. Review scores/texts and reviewer names are **never extracted**, and neither is seller marketing prose ("おすすめポイント" sales copy) — deliberately: review prose is user-generated copyrighted content, and marketing copy stays on the source site. The output is strictly factual vehicle data plus the seller's business identity. Phone numbers are never collected.

**Who is responsible for how the data is used?**
You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms) is your responsibility as the user.

**Are prices accurate?**
Prices are what 55truck.com advertised at retrieval time: `priceJpy` is the vehicle price, `totalPaymentJpy` the advertised total payment including fees. They change constantly — treat them as a snapshot, and re-run for fresh data.

**What about server load?**
Strictly serial requests, ≥1.2 s apart, ~50 vehicles per list page, one extra request per vehicle detail (opt-in), hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If 55truck.com changes its page format, the Actor stops with a clear error instead of silently mis-parsing; if it blocks persistently, the run fails visibly.

### Search terms this Actor answers

japan used truck export · 55truck scraper · トラック王国 scraper · hino isuzu used trucks · japan commercial vehicle data · used dump truck Japan · japan used truck prices · japanese truck export data · used crane truck Japan · refrigerated truck Japan · UD Fuso used trucks · japan heavy equipment export · 中古トラック データ · japan truck auction alternative

### More Japan data Actors by the same developer

- **Japan Used Cars (carsensor.net)** — passenger used-car listings (price, year, mileage, repair history, dealer) from carsensor.net. The passenger-car companion to this truck Actor.
- **Japan Hotels & Ryokan Prices** — hotel/ryokan prices and facility facts from jalan.net.
- **Japan Government Tenders & Awards** — tender notices and award results from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **Japan Care Facilities** — long-term care providers across 35 service types (MHLW open data, CC BY).
- **Japan Government Subsidies & Grants** — open subsidy calls from the official jGrants API.
- **Japan Renewable Energy FIT/FIP Facilities** — METI-certified renewable installations, privacy-safe schema.
- **Japan Financial Licenses & Registrations** — FSA-licensed banks, securities firms, crypto exchanges and more.
- **Japan Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's official register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.

***

*Unofficial tool; not affiliated with 55truck / トラック王国. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data is collected.*

# Actor input Schema

## `maker` (type: `string`):

Optional maker filter, applied upstream via the static maker list pages. English ("Isuzu", "Hino", "Mitsubishi Fuso", "UD Trucks"), Japanese ("いすゞ", "日野") or a 55truck slug ("isuzu"); spellings such as "Mitsubishi-Fuso", "UD", "Fuso" are accepted. Commercial: Isuzu, Hino, Mitsubishi Fuso, UD Trucks, Nissan, Toyota, Mazda, Daihatsu, Mercedes-Benz, Scania, Volvo. Heavy equipment: Komatsu, Hitachi, Kobelco, Kubota, Yanmar, Kato, Tadano, Caterpillar and more. Leave empty for all makers. Example: "Hino".

## `bodyType` (type: `string`):

Optional body-type filter, applied upstream. English ("Dump", "Crane", "Flatbed"), Japanese ("ダンプ", "クレーン") or a 55truck figure slug ("dump", "crane", "flatbody", "coldfreezing", "alumiwing", "mixer", "trailerhead", "forklift" …). Any figure slug from the site's sitemap is accepted. Leave empty for all body types. Example: "dump".

## `size` (type: `string`):

Optional size filter, applied upstream: "small" (小型/2t class), "middle" (中型/4t class), "plus" (増トン) or "big" (大型/10t class). Aliases "large"/"medium"/"2t"/"4t"/"10t" are accepted via the API. Leave empty (All sizes) for every size.

## `model` (type: `string`):

Optional case-insensitive substring filter on the vehicle name as published (e.g. "レンジャー", "プロフィア", "エルフ" — Japanese usually matches best), applied client-side after parsing.

## `priceMin` (type: `integer`):

Optional lower bound on the vehicle price, in 万円 (10,000 JPY units — e.g. 100 = ¥1,000,000). Whole number. Applied client-side.

## `priceMax` (type: `integer`):

Optional upper bound on the vehicle price, in 万円 (10,000 JPY units — e.g. 800 = ¥8,000,000). Whole number. Applied client-side.

## `yearMin` (type: `integer`):

Optional lower bound on the first registration year (年式, 4-digit e.g. 2015). Applied client-side.

## `yearMax` (type: `integer`):

Optional upper bound on the first registration year (4-digit e.g. 2024). Applied client-side.

## `detailFetch` (type: `boolean`):

When true, each vehicle costs one extra request but adds type code (型式), displacement, gross weight, fuel, engine model, seats, body/bed dimensions and the superstructure maker. When false (default) the actor emits list data only (name, prices, year, mileage, load capacity, transmission, emission status, inspection, showroom) — cheaper.

## `maxItems` (type: `integer`):

Stop after this many dataset records (1-10000, default 10).

## `maxApiRequests` (type: `integer`):

Hard budget of HTTP requests to 55truck.com for this run (1-60, default 30; list pages of 50 vehicles + 1 per vehicle detail when detailFetch is on). Requests are strictly serial with >= 1.2 s spacing. When the budget runs out the run completes with complete=false in RUN\_SUMMARY.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. Default: no proxy. Never used for rotation/evasion — one client identity per run.

## Actor input object example

```json
{
  "maker": "Hino",
  "bodyType": "dump",
  "size": "",
  "model": "レンジャー",
  "detailFetch": false,
  "maxItems": 10,
  "maxApiRequests": 30
}
```

# Actor output Schema

## `records` (type: `string`):

Structured used-truck records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maker": "Hino",
    "bodyType": "dump",
    "maxItems": 10,
    "maxApiRequests": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-used-trucks-55truck").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maker": "Hino",
    "bodyType": "dump",
    "maxItems": 10,
    "maxApiRequests": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-used-trucks-55truck").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maker": "Hino",
  "bodyType": "dump",
  "maxItems": 10,
  "maxApiRequests": 30
}' |
apify call jpopendata/japan-used-trucks-55truck --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-used-trucks-55truck"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/PM3P9ecyetilukuAH/builds/H2fmaB2eubkzrzAF7/openapi.json