BIZTRAC BETA
Plumbing installation

MILJØ-OG VARMETEKNIKK AS

Org. no. 942772637 Limited company (AS) Bergen Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 154,000
Operating profit NOK 32,000
Equity NOK 143,000
Incorporated 1987
Share capital NOK 100,000

MILJØ-OG VARMETEKNIKK AS is registered as a limited company in Bergen, Vestland with organisation number 942772637. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor VVS og VA samt hva hermed står i forbindelse, herunder å delta i andre virksomheter med lignende eller annen forretningsdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 154,000 in revenue and NOK 32,000 in operating profit.

Key figures · 2024

Revenue
NOK 154,000
Operating profit
NOK 32,000
Equity
NOK 143,000
Est. value
NOK 171,000

Financial health · 2025

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

Who owns MILJØ-OG VARMETEKNIKK AS?

JAN-ERIK ELVIK
MILJØ-OG VARMETEKNIKK AS
NOK 154,000 rev. · NOK 32,000 profit

MILJØ-OG VARMETEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MILJØ-OG VARMETEKNIKK AS

Who owns MILJØ-OG VARMETEKNIKK AS?

JAN-ERIK ELVIK is the largest registered owner, with 75.0%.

What is the revenue of MILJØ-OG VARMETEKNIKK AS?

MILJØ-OG VARMETEKNIKK AS had revenue of NOK 154,000 in 2024.

Who is the general manager of MILJØ-OG VARMETEKNIKK AS?

Jan-Erik Elvik is registered as general manager of MILJØ-OG VARMETEKNIKK AS.

Where is MILJØ-OG VARMETEKNIKK AS based?

MILJØ-OG VARMETEKNIKK AS has its business address in Øvre Ervik.

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.