BIZTRAC BETA
Restaurant activities

MARVARCONTHE AS

Org. no. 931546511 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 190.0m
Operating profit NOK 2.2m
Equity NOK 14.6m
Incorporated 2023
Employees 208
Share capital NOK 40,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MARVARCONTHE AS is registered as a limited company in Drammen, Buskerud with organisation number 931546511. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 208 registered employees. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Å drive restaurantvirksomhet samt det som hermed står i naturlig forbindelse med dette og annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 190.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 190.0m
Operating profit
NOK 2.2m
Equity
NOK 14.6m
Est. value
NOK 13.6m

Financial health · 2025

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

Who owns MARVARCONTHE AS?

SAGEN HØST AS
MARVARCONTHE AS
NOK 190.0m rev. · NOK 2.2m profit

MARVARCONTHE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARVARCONTHE AS

Who owns MARVARCONTHE AS?

SAGEN HØST AS is the largest registered owner, with 100.0%.

What is the revenue of MARVARCONTHE AS?

MARVARCONTHE AS had revenue of NOK 190.0m in 2025.

Who is the general manager of MARVARCONTHE AS?

Kjetil Sagen Høst is registered as general manager of MARVARCONTHE AS.

Where is MARVARCONTHE AS based?

MARVARCONTHE AS has its business address in Drammen.

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.