biztrac. BETA
COMPANY REGISTER PROFILE
927135213 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

EINERVEGEN HOLDING AS

Org. no. 927135213 Limited company (AS) Verdal Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −26,000
Equity NOK 1.8m
Incorporated 2021
Share capital NOK 30,000

Signals

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

EINERVEGEN HOLDING AS is registered as a limited company in Verdal, Trøndelag with organisation number 927135213. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Holdingselskap for eiendomsselskaper, samt utvikling og oppføring av boligutbyggingsprosjekter, samt utleie av boliger og annet som naturlig hører med dette.”.

Key figures · 2025

Operating profit
NOK −26,000
▲ +2 %
Equity
NOK 1.8m
▼ −28 %
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns EINERVEGEN HOLDING AS?

EINERVEGEN HOLDING AS
· NOK −26,000 profit

EINERVEGEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EINERVEGEN HOLDING AS own?

EINERVEGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EINERVEGEN HOLDING AS

Who owns EINERVEGEN HOLDING AS?

BYGG HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of EINERVEGEN HOLDING AS?

Bjørn Winge is registered as general manager of EINERVEGEN HOLDING AS.

Where is EINERVEGEN HOLDING AS based?

EINERVEGEN HOLDING AS has its business address in Verdal.

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.