BIZTRAC BETA
Office administrative and support activities

JEVNE HOLDING AS

Org. no. 923443142 Limited company (AS) Ås Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 381,000
Operating profit NOK −366,000
Equity NOK 845,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

JEVNE HOLDING AS is registered as a limited company in Ås, Akershus with organisation number 923443142. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 381,000 in revenue and NOK −366,000 in operating profit.

Key figures · 2024

Revenue
NOK 381,000
Operating profit
NOK −366,000
Equity
NOK 845,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns JEVNE HOLDING AS?

BJØRN JEVNE
JEVNE HOLDING AS
NOK 381,000 rev. · NOK −366,000 profit

JEVNE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JEVNE HOLDING AS own?

JEVNE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JEVNE HOLDING AS

Who owns JEVNE HOLDING AS?

BJØRN JEVNE is the largest registered owner, with 100.0%.

What is the revenue of JEVNE HOLDING AS?

JEVNE HOLDING AS had revenue of NOK 381,000 in 2024.

Who is the general manager of JEVNE HOLDING AS?

Bjørn Jevne is registered as general manager of JEVNE HOLDING AS.

Where is JEVNE HOLDING AS based?

JEVNE HOLDING AS has its business address in Ski.

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.