biztrac. BETA
COMPANY REGISTER PROFILE
994934538 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

ENERGY TELLUS AS

Org. no. 994934538 Limited company (AS) Evje Og Hornnes Incorporated 2010 Active
Operating profit NOK −525,000
Equity NOK 2.7m
Incorporated 2010
Share capital NOK 3.7m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−525k kr).

ENERGY TELLUS AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 994934538. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2010. Registered share capital is NOK 3.7m, divided into 3660000 shares. The company's stated purpose is: “Eie samt utvikle selskapet innen for offshore og grønnenergi samt andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −525,000
▼ −2194 %
Equity
NOK 2.7m
▼ −16 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
82.2%
Very good
Equity as a share of total capital

Who owns ENERGY TELLUS AS?

ENERGY TELLUS AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ENERGY TELLUS AS own?

ENERGY TELLUS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENERGY TELLUS AS

Who owns ENERGY TELLUS AS?

SARI AS is the largest registered owner, with 64.3%.

Who is the general manager of ENERGY TELLUS AS?

Erik Risdal is registered as general manager of ENERGY TELLUS AS.

Where is ENERGY TELLUS AS based?

ENERGY TELLUS AS has its business address in Evje.

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.