BIZTRAC BETA
Construction of residential and non-residential buildings

STIAN A. OLSEN AS

Org. no. 918488715 Limited company (AS) Nannestad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 109,000
Operating profit NOK 91,000
Equity NOK 302,000
Incorporated 2017
Share capital NOK 80,000

STIAN A. OLSEN AS is registered as a limited company in Nannestad, Akershus with organisation number 918488715. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 80,000, divided into 400 shares. The company's stated purpose is: “Levere tjenester innen bygg og anlegg, investering i aksjer, verdipapirer, selskaper og selskapsandeler, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 109,000 in revenue and NOK 91,000 in operating profit.

Key figures · 2025

Revenue
NOK 109,000
Operating profit
NOK 91,000
Equity
NOK 302,000
Est. value
NOK 440,000

Financial health · 2025

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

Who owns STIAN A. OLSEN AS?

STIAN ALEXANDER OLSEN
STIAN A. OLSEN AS
NOK 109,000 rev. · NOK 91,000 profit

STIAN A. OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STIAN A. OLSEN AS own?

STIAN A. OLSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STIAN A. OLSEN AS

Who owns STIAN A. OLSEN AS?

STIAN ALEXANDER OLSEN is the largest registered owner, with 100.0%.

What is the revenue of STIAN A. OLSEN AS?

STIAN A. OLSEN AS had revenue of NOK 109,000 in 2025.

Where is STIAN A. OLSEN AS based?

STIAN A. OLSEN AS has its business address in Maura.

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.