biztrac. BETA
COMPANY REGISTER PROFILE
920364144 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VEGARD KEISERÅS AS

Org. no. 920364144 Limited company (AS) Melhus Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK 93,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

VEGARD KEISERÅS AS is registered as a limited company in Melhus, Trøndelag with organisation number 920364144. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Er selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −25,000
▼ −64 %
Equity
NOK 93,000
▼ −5 %
Est. value
NOK 109,000

Financial health · 2025

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
14.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VEGARD KEISERÅS AS?

VEGARD KEISERÅS AS
· NOK −25,000 profit

VEGARD KEISERÅS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VEGARD KEISERÅS AS own?

VEGARD KEISERÅS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEGARD KEISERÅS AS

Who owns VEGARD KEISERÅS AS?

Vegard Keiserås is the largest registered owner, with 100.0%.

Who is the general manager of VEGARD KEISERÅS AS?

Vegard Keiserås is registered as general manager of VEGARD KEISERÅS AS.

Where is VEGARD KEISERÅS AS based?

VEGARD KEISERÅS AS has its business address in Kvål.

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.