BIZTRAC BETA
Rental and operating of own or leased real estate

JET INVESTERING AS

Org. no. 918828850 Limited company (AS) Klepp Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −25,000
Equity NOK 39.9m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).

JET INVESTERING AS is registered as a limited company in Klepp, Rogaland with organisation number 918828850. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper, kjøp salg av verdipapirer samt kjøp, salg og utleie av eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −25,000
Equity
NOK 39.9m
Est. value
NOK 69.3m

Financial health · 2024

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

Who owns JET INVESTERING AS?

JOAKIM ALVÆR
JET INVESTERING AS
NOK 3,000 rev. · NOK −25,000 profit

JET INVESTERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JET INVESTERING AS own?

JET INVESTERING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JET INVESTERING AS

Who owns JET INVESTERING AS?

JOAKIM ALVÆR is the largest registered owner, with 100.0%.

What is the revenue of JET INVESTERING AS?

JET INVESTERING AS had revenue of NOK 3,000 in 2024.

Where is JET INVESTERING AS based?

JET INVESTERING AS has its business address in Bryne.

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.