BIZTRAC BETA
Other support activities for transportation

JETPAK NORGE AS

Org. no. 982404479 Limited company (AS) Ullensaker Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 294.9m
Operating profit NOK 57.8m
Equity NOK 71.5m
Incorporated 2000
Employees 28
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JETPAK NORGE AS is registered as a limited company in Ullensaker, Akershus with organisation number 982404479. The business is classified under other support activities for transportation (NACE 52.260). The company was incorporated in 2000 and has 28 registered employees. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Express transport og relatert logistikkvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 294.9m in revenue and NOK 57.8m in operating profit.

Key figures · 2024

Revenue
NOK 294.9m
Operating profit
NOK 57.8m
Equity
NOK 71.5m
Est. value
NOK 211.8m

Financial health · 2024

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.0%
Very good
Equity as a share of total capital

Who owns JETPAK NORGE AS?

JETPAK GROUP AB
JETPAK NORGE AS
NOK 294.9m rev. · NOK 57.8m profit

JETPAK NORGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JETPAK NORGE AS own?

JETPAK NORGE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JETPAK NORGE AS

Who owns JETPAK NORGE AS?

JETPAK GROUP AB is the largest registered owner, with 100.0%.

What is the revenue of JETPAK NORGE AS?

JETPAK NORGE AS had revenue of NOK 294.9m in 2024.

Where is JETPAK NORGE AS based?

JETPAK NORGE AS has its business address in Gardermoen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.