biztrac. BETA
COMPANY REGISTER PROFILE
897030152 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

JETS HOLDING AS

Org. no. 897030152 Limited company (AS) Bergen Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 175,000
Equity NOK 155,000
Incorporated 2011
Share capital NOK 100,000

JETS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 897030152. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1001 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 175,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +6 %
Operating profit
NOK 175,000
▲ +202 %
Equity
NOK 155,000
▼ −63 %
Est. value
NOK 228,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
1.3%
Weak
Return on total assets
Solidity
0.6%
Not satisfactory
Equity as a share of total capital

Who owns JETS HOLDING AS?

JETS HOLDING AS
NOK 1.5m rev. · NOK 175,000 profit

JETS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JETS HOLDING AS own?

JETS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JETS HOLDING AS

Who owns JETS HOLDING AS?

HØLLELAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JETS HOLDING AS?

JETS HOLDING AS had revenue of NOK 1.5m in 2025.

Where is JETS HOLDING AS based?

JETS HOLDING AS has its business address in Bergen.

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

Report a problem

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