Code summary
Often confused with
- 51102 - Angkutan Udara Niaga Tidak Berjadwal Untuk Penumpang: Compare this code when the main activity is better described as angkutan Udara Niaga Tidak Berjadwal Untuk Penumpang rather than transportasi Antariksa Untuk Penumpang.
- 51101 - Angkutan Udara Niaga Berjadwal Untuk Penumpang: Compare this code when the main activity is better described as angkutan Udara Niaga Berjadwal Untuk Penumpang rather than transportasi Antariksa Untuk Penumpang.
OSS filing review
The OSS review for KBLI 51103 should start from the NIB path, standard certificates, sector licences, and business-model consistency. For transport operators, warehouse businesses, freight actors, and logistics providers, the most common failure point is not the OSS interface itself, but the mismatch between the real activity, the location, and the code being filed.
- Official OSS portal: Validate the NIB path, risk-based flow, and downstream licences for transportasi Antariksa Untuk Penumpang.
- Guide to NIB registration in OSS: Use this checklist to test KBLI consistency, entity data, and whether the team is ready to check the linked KLU before filing as well.
- OSS Risk & licences hub: Open this hub to review the low, medium-low, medium-high, and high-risk flows at system level.
Note: the final per-code risk tier still has to be confirmed directly in OSS.
Core KBJI occupations for KBLI 51103
These occupation groups are linked through a semantic matrix based on the KBLI section and KBJI major groups. The tier is shown so users can distinguish official data from derived links.
- 8 - Plant and machine operators and assemblers
- 4 - Clerical support workers
- 9 - Elementary occupations
Occupation source: BPS KBJI 2014. The current KBLI relation is derived, not an official 1:1 correspondence table.
Region and payroll review
The operating location for KBLI 51103 cannot be separated from region codes, provincial wage floors, and when relevant zone incentives. For transportasi Antariksa Untuk Penumpang, the region review usually starts from the business domicile, the real operating site, and the provincial payroll footprint used by transport operators, warehouse businesses, freight actors, and logistics providers.
- Indonesia region codes: 38 provinces are already loaded with administrative profiles and region codes.
- Minimum wages by province: 38 provincial minimum-wage profiles are available for first-pass payroll screening.
- KEK and FTZ: Check this layer if the business model is sensitive to location incentives or customs facilities.
Source: the Satu Data Indonesia region-code dataset, national wage references, and the official KEK list.
| Level | Code | Description |
|---|---|---|
| Section | H | Transportation and storage |
| Division | 51 | Transportasi Udara |
| Group | 511 | Trasnsportasi Udara Untuk Penumpang |
| Class | 5110 | Trasnportasi Udara Untuk Penumpang |
| Activity | 51103 | Transportasi Antariksa Untuk Penumpang |
Related tools and layers
- KLU 51103
- OSS risk for this code
- Foreign ownership hub
- BPJS calculator
- PPh 21 TER calculator
- Minimum wages by province
Tax norm summary
- 10 provincial capitals norm: 18.0%
- Other provincial capitals norm: 15.0%
- Other areas norm: 14.0%
- Cross-check with DJP before filing tax returns.
Sources
| Source | URL | Regulation | Tier |
|---|---|---|---|
| BPS KBLI 2025 | https://bps.go.id | BPS Regulation No. 7 of 2025 | official |
| Putranto Alliance KLU table | https://putranto-alliance.com/indonesian-business-field-classification-klu/ | Derived from DJP references | fallback |
Compliance risk score
3 of 4 factors passing
- pass Verified in official source - KBLI 2025 code 51103 is present in the official BPS classification release.
- pass Hierarchy chain is complete - Section H, Division 51, Group 511, and Class 5110 are all present in the loaded hierarchy.
- pass Official thresholds documented - A linked KLU/NPPN layer is loaded for KBLI 51103, including published norm values.
- fail Trade or export match available - No BTKI review match is currently loaded for KBLI 51103.
Who is this code for
This code typically applies to the following activity types, operating roles, or business models:
Source: MANUAL, 2026-05-04
FAQ
What is the main operating test for keeping KBLI 51103 under Transportasi Antariksa Untuk Penumpang?
Keep KBLI 51103 when the day-to-day operating core genuinely sits in transportasi Antariksa Untuk Penumpang inside the wider the movement of passengers or goods, storage, and logistics support operations layer. The code is weak if the business only touches that field indirectly while its dominant activity belongs somewhere else.
How should KBLI 51103 be separated from Angkutan Udara Niaga Tidak Berjadwal Untuk Penumpang?
The line is drawn by the actual primary activity carried out at class 5110 and group 511 level. If the operational centre is better described as angkutan Udara Niaga Tidak Berjadwal Untuk Penumpang, the user should compare again instead of keeping KBLI 51103 only because it still sits in the same wider the movement of passengers or goods, storage, and logistics support operations branch.
If the business also performs goods trading, vehicle repair, or separately structured travel services, can KBLI 51103 still remain the lead code?
KBLI 51103 can remain the lead code only when transportasi Antariksa Untuk Penumpang is still the operational and revenue centre. If the dominant line is actually goods trading, vehicle repair, or separately structured travel services, the safer path is to compare neighbouring branches before filing.
Why should transport operators, warehouse businesses, freight actors, and logistics providers still read Group 511 and Class 5110 before selecting KBLI 51103?
Because group and class level show the nearest branch boundary before the endpoint is fixed. Reading those layers first helps the user decide whether transportasi Antariksa Untuk Penumpang is truly the right endpoint or just one of several nearby codes in the same branch.
Which checkpoints still need review after KBLI 51103 is selected?
Choosing KBLI 51103 does not finish the compliance review. After the code is selected, the user still needs to review the OSS risk path, the linked KLU mapping, and the downstream operational checkpoints triggered by filing and implementation.
Changelog
- 2026-03-19 - The code page was published with the official KBLI hierarchy and an activity summary.
- 2026-03-19 - Linked KLU, related tools, and compliance blocks were updated.
This portal is informational. Confirm the final obligation and competent authority before filing, licensing, payroll, tax, or investment decisions. Read methodology.