BIZTRAC BETA
Rental and operating of own or leased real estate

PORTALEN KONTOR AS

Org. no. 992809558 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 54.0m
Operating profit NOK 37.9m
Equity NOK 471.0m
Incorporated 2008
Share capital NOK 130.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PORTALEN KONTOR AS is registered as a limited company in Oslo, Oslo with organisation number 992809558. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 130.5m, divided into 1 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 54.0m in revenue and NOK 37.9m in operating profit.

Key figures · 2025

Revenue
NOK 54.0m
Operating profit
NOK 37.9m
Equity
NOK 471.0m
Est. value
NOK 417.4m

Financial health · 2025

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

Who owns PORTALEN KONTOR AS?

PORTALEN HOLDING AS
PORTALEN KONTOR AS
NOK 54.0m rev. · NOK 37.9m profit

PORTALEN KONTOR AS has 1 registered shareholder:

All shareholders and roles →

Group structure

PORTALEN KONTOR AS er morselskap for 67 datterselskaper:

Frequently asked questions about PORTALEN KONTOR AS

Who owns PORTALEN KONTOR AS?

PORTALEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PORTALEN KONTOR AS?

PORTALEN KONTOR AS had revenue of NOK 54.0m in 2025.

Where is PORTALEN KONTOR AS based?

PORTALEN KONTOR 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.