BIZTRAC BETA
Plumbing installation

FANA RØR OG VEDLIKEHOLD AS

Org. no. 980438546 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 701,000
Equity NOK 6.1m
Incorporated 1998
Share capital NOK 100,000

FANA RØR OG VEDLIKEHOLD AS is registered as a limited company in Bergen, Vestland with organisation number 980438546. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet og hva hermed er forbundet. Selskapet skal også kunne drive annen handel og eie eller på annen måte delta i andre forretningstiltak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 701,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 701,000
Equity
NOK 6.1m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns FANA RØR OG VEDLIKEHOLD AS?

KARSTEN NILSEN
FANA RØR OG VEDLIKEHOLD AS
NOK 4.1m rev. · NOK 701,000 profit

FANA RØR OG VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FANA RØR OG VEDLIKEHOLD AS

Who owns FANA RØR OG VEDLIKEHOLD AS?

KARSTEN NILSEN is the largest registered owner, with 100.0%.

What is the revenue of FANA RØR OG VEDLIKEHOLD AS?

FANA RØR OG VEDLIKEHOLD AS had revenue of NOK 4.1m in 2024.

Who is the general manager of FANA RØR OG VEDLIKEHOLD AS?

Karsten Nilsen is registered as general manager of FANA RØR OG VEDLIKEHOLD AS.

Where is FANA RØR OG VEDLIKEHOLD AS based?

FANA RØR OG VEDLIKEHOLD AS has its business address in Søreidgrend.

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.