BIZTRAC BETA
Joinery installation

EDIR PERFEKT BYGG AS

Org. no. 999513727 Limited company (AS) Asker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK −2,000
Equity NOK 813,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

EDIR PERFEKT BYGG AS is registered as a limited company in Asker, Akershus with organisation number 999513727. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er å utføre et bredt spektrum av byggearbeider, ombygging, bygging, utbygging, oppussingsarbeid og så videre. Samtidig utleie av arbeidskraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK −2,000
Equity
NOK 813,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns EDIR PERFEKT BYGG AS?

IRENEUSZ ANDRZEJ KRYNICKI
EDIR PERFEKT BYGG AS
NOK 4.8m rev. · NOK −2,000 profit

EDIR PERFEKT BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EDIR PERFEKT BYGG AS

Who owns EDIR PERFEKT BYGG AS?

IRENEUSZ ANDRZEJ KRYNICKI is the largest registered owner, with 50.0%.

What is the revenue of EDIR PERFEKT BYGG AS?

EDIR PERFEKT BYGG AS had revenue of NOK 4.8m in 2025.

Who is the general manager of EDIR PERFEKT BYGG AS?

Edyta Krynicka is registered as general manager of EDIR PERFEKT BYGG AS.

Where is EDIR PERFEKT BYGG AS based?

EDIR PERFEKT BYGG AS has its business address in Nesbru.

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.