BIZTRAC BETA
Plumbing installation

JOHNSEN RØRSERVICE AS

Org. no. 918446370 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK −100,000
Equity NOK 57,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−100k kr).

JOHNSEN RØRSERVICE AS is registered as a limited company in Bergen, Vestland with organisation number 918446370. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørleggervirksomhet og annet som naturlig faller sammen med dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK −100,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK −100,000
Equity
NOK 57,000
Est. value
NOK 486,000

Financial health · 2024

Liquidity
0.70
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JOHNSEN RØRSERVICE AS?

FREDRIK JOHNSEN
JOHNSEN RØRSERVICE AS
NOK 1.3m rev. · NOK −100,000 profit

JOHNSEN RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOHNSEN RØRSERVICE AS

Who owns JOHNSEN RØRSERVICE AS?

FREDRIK JOHNSEN is the largest registered owner, with 100.0%.

What is the revenue of JOHNSEN RØRSERVICE AS?

JOHNSEN RØRSERVICE AS had revenue of NOK 1.3m in 2024.

Who is the general manager of JOHNSEN RØRSERVICE AS?

Fredrik Johnsen is registered as general manager of JOHNSEN RØRSERVICE AS.

Where is JOHNSEN RØRSERVICE AS based?

JOHNSEN RØRSERVICE AS has its business address in Bønes.

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.