biztrac. BETA
COMPANY REGISTER PROFILE
979212445 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

JOHANSEN VVS AS

Org. no. 979212445 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 224,000
Equity NOK 439,000
Incorporated 1997
Share capital NOK 100,000

JOHANSEN VVS AS is registered as a limited company in Oslo, Oslo with organisation number 979212445. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Rehabilitering, nyanlegg, sanitæranlegg, kjøleanlegg og annen virksomhet i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 224,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
▲ +77 %
Operating profit
NOK 224,000
▲ +100 %
Equity
NOK 439,000
▲ +58 %
Est. value
NOK 827,000

Financial health · 2025

Liquidity
1.86
Good
Current assets ÷ current liabilities
Profitability
13.6%
Good
Return on total assets
Solidity
21.7%
Good
Equity as a share of total capital

Who owns JOHANSEN VVS AS?

JOHANSEN VVS AS
NOK 3.8m rev. · NOK 224,000 profit

JOHANSEN VVS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JOHANSEN VVS AS own?

JOHANSEN VVS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOHANSEN VVS AS

Who owns JOHANSEN VVS AS?

Morten Johansen is the largest registered owner, with 90.0%.

What is the revenue of JOHANSEN VVS AS?

JOHANSEN VVS AS had revenue of NOK 3.8m in 2025.

Who is the general manager of JOHANSEN VVS AS?

Morten Johansen is registered as general manager of JOHANSEN VVS AS.

Where is JOHANSEN VVS AS based?

JOHANSEN VVS AS has its business address in Oslo.

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

Report a problem

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