BIZTRAC BETA
Civil engineering activities

VIAL ENERGY AS

Org. no. 928222675 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 11.1m
Operating profit NOK 3.5m
Equity NOK 1.3m
Incorporated 2021
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.

VIAL ENERGY AS is registered as a limited company in Stavanger, Rogaland with organisation number 928222675. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivning innen infrastruktur, byggeteknikk, energiløsninger og mulighetsutvikling, samt herved står i forbindelse, herunder delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.1m in revenue and NOK 3.5m in operating profit.

Key figures · 2025

Revenue
NOK 11.1m
Operating profit
NOK 3.5m
Equity
NOK 1.3m
Est. value
NOK 12.1m

Financial health · 2025

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

Who owns VIAL ENERGY AS?

VIAL AS
VIAL ENERGY AS
NOK 11.1m rev. · NOK 3.5m profit

VIAL ENERGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIAL ENERGY AS

Who owns VIAL ENERGY AS?

VIAL AS is the largest registered owner, with 100.0%.

What is the revenue of VIAL ENERGY AS?

VIAL ENERGY AS had revenue of NOK 11.1m in 2025.

Who is the general manager of VIAL ENERGY AS?

Rune Jonassen is registered as general manager of VIAL ENERGY AS.

Where is VIAL ENERGY AS based?

VIAL ENERGY AS has its business address in Stavanger.

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.