BIZTRAC BETA
Other technical consultancy

ERRYCO ENERGY AS

Org. no. 928293742 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −194,000
Equity NOK 30.3m
Incorporated 2021
Share capital NOK 77,000

Signals

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

ERRYCO ENERGY AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928293742. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 77,000, divided into 76536 shares. The company's stated purpose is: “Investering i og drift av alle typer energirelatert virksomhet som i produksjon, lagring, transport og bruk, inklusive innsatsfaktorer for slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −194,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −194,000
Equity
NOK 30.3m
Est. value
NOK 18.9m

Financial health · 2024

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

Who owns ERRYCO ENERGY AS?

ERLING RYTTER
ERRYCO ENERGY AS
NOK 10,000 rev. · NOK −194,000 profit

ERRYCO ENERGY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERRYCO ENERGY AS own?

ERRYCO ENERGY AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about ERRYCO ENERGY AS

Who owns ERRYCO ENERGY AS?

ERLING RYTTER is the largest registered owner, with 100.0%.

What is the revenue of ERRYCO ENERGY AS?

ERRYCO ENERGY AS had revenue of NOK 10,000 in 2024.

Where is ERRYCO ENERGY AS based?

ERRYCO ENERGY AS has its business address in Trondheim.

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.