BIZTRAC BETA
Rental and operating of own or leased real estate

PORSGRUNN KONTORBYGG HOLDING AS

Org. no. 994881884 Limited company (AS) Porsgrunn Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 32.1m
Operating profit NOK 23.5m
Equity NOK 54.9m
Incorporated 2009
Share capital NOK 1.1m

Signals

1 flags
  • Nylig endring 2026-04-10 Adresseendring registrert 2026-04-10.

PORSGRUNN KONTORBYGG HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 994881884. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 1.1m, divided into 1067200 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 32.1m in revenue and NOK 23.5m in operating profit.

Key figures · 2025

Revenue
NOK 32.1m
Operating profit
NOK 23.5m
Equity
NOK 54.9m
Est. value
NOK 72.1m

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.0%
Good
Equity as a share of total capital

Who owns PORSGRUNN KONTORBYGG HOLDING AS?

LØREN HOLDING AS
PORSGRUNN KONTORBYGG HOLDING AS
NOK 32.1m rev. · NOK 23.5m profit

PORSGRUNN KONTORBYGG HOLDING AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about PORSGRUNN KONTORBYGG HOLDING AS

Who owns PORSGRUNN KONTORBYGG HOLDING AS?

LØREN HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of PORSGRUNN KONTORBYGG HOLDING AS?

PORSGRUNN KONTORBYGG HOLDING AS had revenue of NOK 32.1m in 2025.

Where is PORSGRUNN KONTORBYGG HOLDING AS based?

PORSGRUNN KONTORBYGG HOLDING AS has its business address in Porsgrunn.

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.