BIZTRAC BETA
Other technical consultancy

CH4 ENGINEERING AS

Org. no. 820438302 Limited company (AS) Farsund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK 1.3m
Equity NOK 696,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CH4 ENGINEERING AS is registered as a limited company in Farsund, Agder with organisation number 820438302. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Selskapets formål er rådgivning, engineering, utvikling innen energianlegg og deltakelse i andre selskap”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK 1.3m
Equity
NOK 696,000
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.6%
Satisfactory
Equity as a share of total capital

Who owns CH4 ENGINEERING AS?

ANERO AS
CH4 ENGINEERING AS
NOK 6.8m rev. · NOK 1.3m profit

CH4 ENGINEERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CH4 ENGINEERING AS

Who owns CH4 ENGINEERING AS?

ANERO AS is the largest registered owner, with 51.0%.

What is the revenue of CH4 ENGINEERING AS?

CH4 ENGINEERING AS had revenue of NOK 6.8m in 2025.

Who is the general manager of CH4 ENGINEERING AS?

Harry Leo Nøttveit is registered as general manager of CH4 ENGINEERING AS.

Where is CH4 ENGINEERING AS based?

CH4 ENGINEERING AS has its business address in Vanse.

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.