BIZTRAC BETA
COMPANY REGISTER PROFILE
933885933 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

JEVNE INVEST AS

Org. no. 933885933 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

JEVNE INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 933885933. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap med fokus på oppstart av selskap, noterte/unoterte aksjer og andre aktivaklasser.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 15,000
Est. value
NOK 18,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JEVNE INVEST AS?

SIMEN JEVNE ARNESEN
JEVNE INVEST AS
NOK 0 rev. · NOK −7,000 profit

JEVNE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JEVNE INVEST AS

Who owns JEVNE INVEST AS?

SIMEN JEVNE ARNESEN is the largest registered owner, with 100.0%.

What is the revenue of JEVNE INVEST AS?

JEVNE INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of JEVNE INVEST AS?

Simen Jevne Arnesen is registered as general manager of JEVNE INVEST AS.

Where is JEVNE INVEST AS based?

JEVNE INVEST AS has its business address in Oslo.

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.