biztrac. BETA
COMPANY REGISTER PROFILE
916808003 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SØNSTERUDVEIEN 26 AS

Org. no. 916808003 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −455,000
Equity NOK 944,000
Incorporated 2016
Share capital NOK 100,000

Signals

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

SØNSTERUDVEIEN 26 AS is registered as a limited company in Oslo, Oslo with organisation number 916808003. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverve, forvalte aksjer, andre finansplasseringer og faste eiendommer, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −455,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
▲ +25 %
Operating profit
NOK −455,000
▲ +84 %
Equity
NOK 944,000
▲ +119 %
Est. value
NOK 862,000

Financial health · 2025

Liquidity
7.32
Very good
Current assets ÷ current liabilities
Profitability
-1.5%
Not satisfactory
Return on total assets
Solidity
2.8%
Not satisfactory
Equity as a share of total capital

Who owns SØNSTERUDVEIEN 26 AS?

SØNSTERUDVEIEN 26 AS
NOK 2.3m rev. · NOK −455,000 profit

SØNSTERUDVEIEN 26 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØNSTERUDVEIEN 26 AS

Who owns SØNSTERUDVEIEN 26 AS?

ESTATEC AS is the largest registered owner, with 100.0%.

What is the revenue of SØNSTERUDVEIEN 26 AS?

SØNSTERUDVEIEN 26 AS had revenue of NOK 2.3m in 2025.

Where is SØNSTERUDVEIEN 26 AS based?

SØNSTERUDVEIEN 26 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 03.10.2026.

Report a problem

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