BIZTRAC BETA
Restaurant activities

VÆRK AS

Org. no. 920708366 Limited company (AS) Fredrikstad Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 10,000
Equity NOK 3,000
Incorporated 2018
Employees 16
Share capital NOK 102,000

VÆRK AS is registered as a limited company in Fredrikstad, Østfold with organisation number 920708366. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 16 registered employees. Registered share capital is NOK 102,000, divided into 3000 shares. The company's stated purpose is: “Restaurant, bar og catering drift og det som står i naturlig forbindelse med dette. Virksomheten skal også fokusere på kurs/ konferanser, kulturarrangementer og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 10,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 10,000
Equity
NOK 3,000
Est. value
NOK 49,000

Financial health · 2025

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

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

Who owns VÆRK AS?

MEDITEK AS
VÆRK AS
NOK 6.2m rev. · NOK 10,000 profit

VÆRK AS has 3 registered shareholders:

All shareholders and roles →

Group structure

VÆRK AS er morselskap for 1 datterselskap:

Frequently asked questions about VÆRK AS

Who owns VÆRK AS?

MEDITEK AS is the largest registered owner, with 90.0%.

What is the revenue of VÆRK AS?

VÆRK AS had revenue of NOK 6.2m in 2025.

Who is the general manager of VÆRK AS?

Erlend Julius Dalsegg Bertelsen is registered as general manager of VÆRK AS.

Where is VÆRK AS based?

VÆRK AS has its business address in Gamle Fredrikstad.

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.