BIZTRAC BETA
Rental and operating of own or leased real estate

VINKEL ENERGY AS

Org. no. 917635307 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −32,000
Equity NOK 227,000
Incorporated 2016
Share capital NOK 100,000

Signals

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

VINKEL ENERGY AS is registered as a limited company in Stavanger, Rogaland with organisation number 917635307. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Generell investeringsvirksomhet i fast eiendom, utleie av fast eiendom, levere konsulenttjenester, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −32,000
Equity
NOK 227,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns VINKEL ENERGY AS?

VINKEL INVEST AS
VINKEL ENERGY AS
NOK 0 rev. · NOK −32,000 profit

VINKEL ENERGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINKEL ENERGY AS

Who owns VINKEL ENERGY AS?

VINKEL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VINKEL ENERGY AS?

VINKEL ENERGY AS had revenue of NOK 0 in 2025.

Who is the general manager of VINKEL ENERGY AS?

Steffen Evertsen is registered as general manager of VINKEL ENERGY AS.

Where is VINKEL ENERGY AS based?

VINKEL 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.