BIZTRAC BETA
Rental and operating of own or leased real estate

PUSTUTVEIEN 6-14 AS

Org. no. 989699008 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 39.3m
Operating profit NOK 24.5m
Equity NOK 250.0m
Incorporated 2005
Share capital NOK 2.6m

Signals

1 flags
  • Nylig endring 2026-06-03 Adresseendring registrert 2026-06-03.

PUSTUTVEIEN 6-14 AS is registered as a limited company in Oslo, Oslo with organisation number 989699008. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.6m, divided into 26000 shares. The company's stated purpose is: “Eie, kjøpe, selge og leie ut fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.3m in revenue and NOK 24.5m in operating profit.

Key figures · 2025

Revenue
NOK 39.3m
Operating profit
NOK 24.5m
Equity
NOK 250.0m
Est. value
NOK 229.6m

Financial health · 2025

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

Who owns PUSTUTVEIEN 6-14 AS?

COOP NORGE EIENDOM AS
PUSTUTVEIEN 6-14 AS
NOK 39.3m rev. · NOK 24.5m profit

PUSTUTVEIEN 6-14 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

PUSTUTVEIEN 6-14 AS er morselskap for 10 datterselskaper:

Frequently asked questions about PUSTUTVEIEN 6-14 AS

Who owns PUSTUTVEIEN 6-14 AS?

COOP NORGE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of PUSTUTVEIEN 6-14 AS?

PUSTUTVEIEN 6-14 AS had revenue of NOK 39.3m in 2025.

Where is PUSTUTVEIEN 6-14 AS based?

PUSTUTVEIEN 6-14 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 15.06.2026.

Report a problem

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