biztrac. BETA
COMPANY REGISTER PROFILE
916946864 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Beverage serving activities

MELLOMBELS AS

Org. no. 916946864 Limited company (AS) Time Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 10.2m
Operating profit NOK 1.6m
Equity NOK 1.0m
Incorporated 2016
Employees 16
Share capital NOK 430,000

MELLOMBELS AS is registered as a limited company in Time, Rogaland with organisation number 916946864. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2016 and has 16 registered employees. Registered share capital is NOK 430,000, divided into 4300 shares. The company's stated purpose is: “Drift av pub og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 10.2m
▲ +31 %
Operating profit
NOK 1.6m
▲ +125 %
Equity
NOK 1.0m
▲ +22 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
43.6%
Very good
Return on total assets
Solidity
21.9%
Good
Equity as a share of total capital

Who owns MELLOMBELS AS?

MELLOMBELS AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about MELLOMBELS AS

Who owns MELLOMBELS AS?

2MT HOLDING AS is the largest registered owner, with 27.5%.

What is the revenue of MELLOMBELS AS?

MELLOMBELS AS had revenue of NOK 10.2m in 2025.

Who is the general manager of MELLOMBELS AS?

Ørjan Kønig is registered as general manager of MELLOMBELS AS.

Where is MELLOMBELS AS based?

MELLOMBELS AS has its business address in Bryne.

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.