BIZTRAC BETA
Uoppgitt

SJEG INVEST AS

Org. no. 931544071 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 2.5m
Incorporated 2023
Share capital NOK 40,000

Signals

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

SJEG INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 931544071. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 2.5m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns SJEG INVEST AS?

SJUR JOHANNES BORGERSEN KVAMME
SJEG INVEST AS
NOK 0 rev. · NOK −3,000 profit

SJEG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SJEG INVEST AS own?

SJEG INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SJEG INVEST AS

Who owns SJEG INVEST AS?

SJUR JOHANNES BORGERSEN KVAMME is the largest registered owner, with 100.0%.

What is the revenue of SJEG INVEST AS?

SJEG INVEST AS had revenue of NOK 0 in 2024.

Where is SJEG INVEST AS based?

SJEG 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.