BIZTRAC BETA
COMPANY REGISTER PROFILE
933399206 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SKJENNUNGEN INVEST AS

Org. no. 933399206 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 15,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

SKJENNUNGEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 933399206. 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: “Salg av konsulenttjenester og produkter, og å investere i verdipapirer og andre investeringsobjekter, samt å eie eller delta i andre virksomheter med et hvert formål.”.

Key figures · 2025

Operating profit
NOK −9,000
Equity
NOK 15,000
▼ −51 %
Est. value
NOK 17,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.7%
Weak
Equity as a share of total capital

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

Who owns SKJENNUNGEN INVEST AS?

SKJENNUNGEN INVEST AS
· NOK −9,000 profit

SKJENNUNGEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKJENNUNGEN INVEST AS own?

SKJENNUNGEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKJENNUNGEN INVEST AS

Who owns SKJENNUNGEN INVEST AS?

PÅL ANDRE LÅHNE is the largest registered owner, with 100.0%.

Who is the general manager of SKJENNUNGEN INVEST AS?

Pål Andre Låhne is registered as general manager of SKJENNUNGEN INVEST AS.

Where is SKJENNUNGEN INVEST AS based?

SKJENNUNGEN 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 25.08.2026.

Report a problem

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