BIZTRAC BETA
Buying and selling of own real estate

VEGEBAKKEN AS

Org. no. 987061812 Limited company (AS) Bergen Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK 5.8m
Equity NOK 5.2m
Incorporated 2004
Share capital NOK 449,000

VEGEBAKKEN AS is registered as a limited company in Bergen, Vestland with organisation number 987061812. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2004. Registered share capital is NOK 449,000, divided into 100 shares. The company's stated purpose is: “Yte lån, investere i eiendom, valuta og finansielle verdipapirer, herunder lånefinansierte investeringer og derivater av forannevnte, samt annen virksomhet i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 5.8m in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK 5.8m
Equity
NOK 5.2m
Est. value
NOK 14.4m

Financial health · 2025

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

Who owns VEGEBAKKEN AS?

SVEIN OSLAND
VEGEBAKKEN AS
NOK 5.9m rev. · NOK 5.8m profit

VEGEBAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VEGEBAKKEN AS own?

VEGEBAKKEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VEGEBAKKEN AS

Who owns VEGEBAKKEN AS?

SVEIN OSLAND is the largest registered owner, with 100.0%.

What is the revenue of VEGEBAKKEN AS?

VEGEBAKKEN AS had revenue of NOK 5.9m in 2025.

Who is the general manager of VEGEBAKKEN AS?

Svein Osland is registered as general manager of VEGEBAKKEN AS.

Where is VEGEBAKKEN AS based?

VEGEBAKKEN AS has its business address in Nyborg.

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.