BIZTRAC BETA
Construction of residential and non-residential buildings

PM PERFEKT BYGG AS

Org. no. 930769347 Limited company (AS) Lier Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK −42,000
Equity NOK 211,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

Signals

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

PM PERFEKT BYGG AS is registered as a limited company in Lier, Buskerud with organisation number 930769347. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rehabilitering og oppussing av bygninger. Terrasser. Male-, tømre- og snekkerarbeid samt andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK −42,000
Equity
NOK 211,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.4%
Satisfactory
Equity as a share of total capital

Who owns PM PERFEKT BYGG AS?

MACIEJ ZAJACZKOWSKI
PM PERFEKT BYGG AS
NOK 3.5m rev. · NOK −42,000 profit

PM PERFEKT BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PM PERFEKT BYGG AS

Who owns PM PERFEKT BYGG AS?

MACIEJ ZAJACZKOWSKI is the largest registered owner, with 50.0%.

What is the revenue of PM PERFEKT BYGG AS?

PM PERFEKT BYGG AS had revenue of NOK 3.5m in 2025.

Where is PM PERFEKT BYGG AS based?

PM PERFEKT BYGG AS has its business address in Sylling.

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.