BIZTRAC BETA
Restaurant activities

WERGELAND RESTAURANTDRIFT AS

Org. no. 927290138 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 84,000
Equity NOK 9,000
Incorporated 2021
Employees 13
Share capital NOK 100,000

WERGELAND RESTAURANTDRIFT AS is registered as a limited company in Bergen, Vestland with organisation number 927290138. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Drift av restaurant.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 84,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 84,000
Equity
NOK 9,000
Est. value
NOK 318,000

Financial health · 2024

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.1%
Weak
Equity as a share of total capital

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

Who owns WERGELAND RESTAURANTDRIFT AS?

STEFANO TAVASSI
WERGELAND RESTAURANTDRIFT AS
NOK 4.6m rev. · NOK 84,000 profit

WERGELAND RESTAURANTDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WERGELAND RESTAURANTDRIFT AS

Who owns WERGELAND RESTAURANTDRIFT AS?

STEFANO TAVASSI is the largest registered owner, with 100.0%.

What is the revenue of WERGELAND RESTAURANTDRIFT AS?

WERGELAND RESTAURANTDRIFT AS had revenue of NOK 4.6m in 2024.

Who is the general manager of WERGELAND RESTAURANTDRIFT AS?

Stefano Tavassi is registered as general manager of WERGELAND RESTAURANTDRIFT AS.

Where is WERGELAND RESTAURANTDRIFT AS based?

WERGELAND RESTAURANTDRIFT 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.