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

AMMERUDVEIEN 19-25 AS

Org. no. 916349114 Limited company (AS) Oslo Incorporated 2015 Active
Revenue 2025 NOK 2.4m
Operating profit NOK 1.4m
Equity NOK 19.8m
Incorporated 2015
Share capital NOK 41,000

Signals

1 flags
  • Nylig endring 2026-09-21 Adresseendring registrert 2026-09-21.

AMMERUDVEIEN 19-25 AS is registered as a limited company in Oslo, Oslo with organisation number 916349114. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 41,000, divided into 100 shares. The company's stated purpose is: “Handels-, investerings- og eiendomsvirksomhet, samt å delta i andre selskaper med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 1.4m in operating profit.

Former names: OBOS AMMERUDVEIEN 25 AS

Key figures · 2025

Revenue
NOK 2.4m
▲ +21 %
Operating profit
NOK 1.4m
▲ +26 %
Equity
NOK 19.8m
▼ −0 %
Est. value
NOK 17.0m

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
5.2%
Weak
Return on total assets
Solidity
78.7%
Very good
Equity as a share of total capital

Who owns AMMERUDVEIEN 19-25 AS?

AMMERUDVEIEN 19-25 AS
NOK 2.4m rev. · NOK 1.4m profit

AMMERUDVEIEN 19-25 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMMERUDVEIEN 19-25 AS

Who owns AMMERUDVEIEN 19-25 AS?

HEIMSTADEN BOSTAD INVEST 10 AS is the largest registered owner, with 100.0%.

What is the revenue of AMMERUDVEIEN 19-25 AS?

AMMERUDVEIEN 19-25 AS had revenue of NOK 2.4m in 2025.

Where is AMMERUDVEIEN 19-25 AS based?

AMMERUDVEIEN 19-25 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.