BIZTRAC BETA
COMPANY REGISTER PROFILE
912154882 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Production of electricity from hydropower

VÆLA KRAFT AS

Org. no. 912154882 Limited company (AS) Tydal Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 776,000
Operating profit NOK −399,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 1.9m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−399k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VÆLA KRAFT AS is registered as a limited company in Tydal, Trøndelag with organisation number 912154882. The business is classified under production of electricity from hydropower (NACE 35.121). The company was incorporated in 2013. Registered share capital is NOK 1.9m, divided into 1871600 shares. The company's stated purpose is: “Prosjektering, investering og drift av småkraftverk i Tydal kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 776,000 in revenue and NOK −399,000 in operating profit.

Key figures · 2025

Revenue
NOK 776,000
▲ +25 %
Operating profit
NOK −399,000
▲ +18 %
Equity
NOK 1.1m
▲ +143 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
65.96
Very good
Current assets ÷ current liabilities
Profitability
-2.0%
Not satisfactory
Return on total assets
Solidity
5.1%
Weak
Equity as a share of total capital

Who owns VÆLA KRAFT AS?

VÆLA KRAFT AS
NOK 776,000 rev. · NOK −399,000 profit

VÆLA KRAFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÆLA KRAFT AS

Who owns VÆLA KRAFT AS?

CK BOND AS is the largest registered owner, with 100.0%.

What is the revenue of VÆLA KRAFT AS?

VÆLA KRAFT AS had revenue of NOK 776,000 in 2025.

Where is VÆLA KRAFT AS based?

VÆLA KRAFT AS has its business address in Tydal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.