BIZTRAC BETA
COMPANY REGISTER PROFILE
927493268 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

O37 INVEST AS

Org. no. 927493268 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 2.6m
Incorporated 2021
Share capital NOK 30,000

Signals

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

O37 INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 927493268. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i selskaper, andre finansielle aktiva, fast eiendom, og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −14,000
▼ −57 %
Equity
NOK 2.6m
▲ +11 %
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns O37 INVEST AS?

O37 INVEST AS
· NOK −14,000 profit

O37 INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O37 INVEST AS

Who owns O37 INVEST AS?

KRISTIN HEGSTAD is the largest registered owner, with 100.0%.

Where is O37 INVEST AS based?

O37 INVEST AS has its business address in Oslo.

Property

Business address Roald Amundsens gate 6, 0161 Oslo
Cadastral unit 301-209/355/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

54 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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