biztrac. BETA
COMPANY REGISTER PROFILE
930758590 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

BASSO BERGEN AS

Org. no. 930758590 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 28.5m
Operating profit NOK 5.4m
Equity NOK 2.0m
Incorporated 2022
Employees 34
Share capital NOK 30,000

BASSO BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 930758590. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 34 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Restaurantvirksomhet, servering, samt alt hva hermed står i forbindelse, herunder deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.5m in revenue and NOK 5.4m in operating profit.

Key figures · 2025

Revenue
NOK 28.5m
▲ +11 %
Operating profit
NOK 5.4m
▲ +113 %
Equity
NOK 2.0m
▲ +6570 %
Est. value
NOK 15.6m

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
59.7%
Very good
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns BASSO BERGEN AS?

BASSO BERGEN AS
NOK 28.5m rev. · NOK 5.4m profit

BASSO BERGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BASSO BERGEN AS

Who owns BASSO BERGEN AS?

DININGSIX NORGE HOLDING AS is the largest registered owner, with 90.0%.

What is the revenue of BASSO BERGEN AS?

BASSO BERGEN AS had revenue of NOK 28.5m in 2025.

Who is the general manager of BASSO BERGEN AS?

Lasse Juul Horn is registered as general manager of BASSO BERGEN AS.

Where is BASSO BERGEN AS based?

BASSO BERGEN AS has its business address in Bergen.

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.