BIZTRAC BETA
Uoppgitt

OISANN INVEST AS

Org. no. 927387263 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7
Equity NOK 2.5m
Incorporated 2021
Share capital NOK 30,000

Signals

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

OISANN INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 927387263. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie selskaper eller andeler av selskaper med virksomhet relatert til entreprenørvirksomhet, salg og konsulentvirksomhet, samt hva hermed står i forbindelse. Selskapet kan videre eie og drive fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7
Equity
NOK 2.5m
Est. value
NOK 17.8m

Financial health · 2025

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

Who owns OISANN INVEST AS?

KRISTOFFER KRANSBERG-PETTERSEN
OISANN INVEST AS
NOK 0 rev. · NOK −7 profit

OISANN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OISANN INVEST AS own?

OISANN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OISANN INVEST AS

Who owns OISANN INVEST AS?

KRISTOFFER KRANSBERG-PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of OISANN INVEST AS?

OISANN INVEST AS had revenue of NOK 0 in 2025.

Where is OISANN INVEST AS based?

OISANN INVEST AS has its business address in Drammen.

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.