BIZTRAC BETA
COMPANY REGISTER PROFILE
896956922 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Plumbing installation

EGGEDAL RØR AS

Org. no. 896956922 Limited company (AS) Sigdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 486,000
Equity NOK 962,000
Incorporated 2011
Share capital NOK 100,000

EGGEDAL RØR AS is registered as a limited company in Sigdal, Buskerud with organisation number 896956922. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Rørleggervirksomhet, industrimekanikk, kjøp og salg av utstyr samt annen virksomhet som faller naturlig inn under dette, herunder deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 486,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▲ +20 %
Operating profit
NOK 486,000
▼ −15 %
Equity
NOK 962,000
▲ +28 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
2.21
Very good
Current assets ÷ current liabilities
Profitability
36.9%
Very good
Return on total assets
Solidity
63.4%
Very good
Equity as a share of total capital

Who owns EGGEDAL RØR AS?

EGGEDAL RØR AS
NOK 2.4m rev. · NOK 486,000 profit

EGGEDAL RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EGGEDAL RØR AS

Who owns EGGEDAL RØR AS?

GISLE KRISTOFFER LØVLID is the largest registered owner, with 100.0%.

What is the revenue of EGGEDAL RØR AS?

EGGEDAL RØR AS had revenue of NOK 2.4m in 2025.

Who is the general manager of EGGEDAL RØR AS?

Gisle Kristoffer Løvlid is registered as general manager of EGGEDAL RØR AS.

Where is EGGEDAL RØR AS based?

EGGEDAL RØR AS has its business address in Nedre Eggedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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