BIZTRAC BETA
Hotels and similar accommodation

VEGA KRO OG MOTELL AS

Org. no. 914736684 Limited company (AS) Vega Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −157,000
Equity NOK 1.0m
Incorporated 2014
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−157k kr).

VEGA KRO OG MOTELL AS is registered as a limited company in Vega, Nordland with organisation number 914736684. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Eie,drive og utleie av kro og motell ogDrift og utlei annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −157,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −157,000
Equity
NOK 1.0m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns VEGA KRO OG MOTELL AS?

BÅRD KARLSEN
VEGA KRO OG MOTELL AS
NOK 1.7m rev. · NOK −157,000 profit

VEGA KRO OG MOTELL AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEGA KRO OG MOTELL AS

Who owns VEGA KRO OG MOTELL AS?

BÅRD KARLSEN is the largest registered owner, with 60.0%.

What is the revenue of VEGA KRO OG MOTELL AS?

VEGA KRO OG MOTELL AS had revenue of NOK 1.7m in 2024.

Where is VEGA KRO OG MOTELL AS based?

VEGA KRO OG MOTELL AS has its business address in Vega.

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.