BIZTRAC BETA
Manufacture of gas

SVANEM BIOGASS AS

Org. no. 927048280 Limited company (AS) Heim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 223,000
Equity NOK −1.3m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).

SVANEM BIOGASS AS is registered as a limited company in Heim, Trøndelag with organisation number 927048280. The business is classified under manufacture of gas (NACE 35.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å være et driftsselskap for drift av tekniske installasjoner og alt som står i dens forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 223,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 223,000
Equity
NOK −1.3m
Est. value
NOK 1.2m

Financial health · 2025

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

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

Who owns SVANEM BIOGASS AS?

SVANEM BIOGASS HOLDING AS
SVANEM BIOGASS AS
NOK 4.6m rev. · NOK 223,000 profit

SVANEM BIOGASS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVANEM BIOGASS AS

Who owns SVANEM BIOGASS AS?

SVANEM BIOGASS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SVANEM BIOGASS AS?

SVANEM BIOGASS AS had revenue of NOK 4.6m in 2025.

Who is the general manager of SVANEM BIOGASS AS?

Roar Lian Svanem is registered as general manager of SVANEM BIOGASS AS.

Where is SVANEM BIOGASS AS based?

SVANEM BIOGASS AS has its business address in Hellandsjøen.

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.