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

ØSTBY AS

Org. no. 924572213 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 1.0m
Incorporated 2020
Share capital NOK 100,000

Signals

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

ØSTBY AS is registered as a limited company in Oslo, Oslo with organisation number 924572213. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forvaltning av kapital og andre investeringer.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK 1.0m
▼ −1 %
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns ØSTBY AS?

ØSTBY AS
· NOK −13,000 profit

ØSTBY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØSTBY AS own?

ØSTBY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ØSTBY AS

Who owns ØSTBY AS?

GUNNAR ØSTBY is the largest registered owner, with 100.0%.

Where is ØSTBY AS based?

ØSTBY AS has its business address in Oslo.

Property

Business address Sørkedalsveien 258F, 0754 Oslo
Cadastral unit 301-27/2708/0/0
Building Tomannsbolig, vertikal · 1 unit

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