BIZTRAC BETA
Manufacture of bread; manufacture of fresh pastry goods and cakes

RØROS MAT OG CATERING AS

Org. no. 920223923 Limited company (AS) Røros Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 292,000
Equity NOK 734,000
Incorporated 2017
Employees 27
Share capital NOK 400,000

RØROS MAT OG CATERING AS is registered as a limited company in Røros, Trøndelag with organisation number 920223923. The business is classified under manufacture of bread; manufacture of fresh pastry goods and cakes (NACE 10.710). The company was incorporated in 2017 and has 27 registered employees. Registered share capital is NOK 400,000, divided into 1000 shares. The company's stated purpose is: “Bakeri og kaffeteria /m Catering.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 292,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 292,000
Equity
NOK 734,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
2.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.5%
Good
Equity as a share of total capital

Who owns RØROS MAT OG CATERING AS?

FREDRIK THØRN KOLBERG
RØROS MAT OG CATERING AS
NOK 9.5m rev. · NOK 292,000 profit

RØROS MAT OG CATERING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØROS MAT OG CATERING AS

Who owns RØROS MAT OG CATERING AS?

FREDRIK THØRN KOLBERG is the largest registered owner, with 25.0%.

What is the revenue of RØROS MAT OG CATERING AS?

RØROS MAT OG CATERING AS had revenue of NOK 9.5m in 2024.

Who is the general manager of RØROS MAT OG CATERING AS?

Kenneth Kolberg Sigvartsen is registered as general manager of RØROS MAT OG CATERING AS.

Where is RØROS MAT OG CATERING AS based?

RØROS MAT OG CATERING AS has its business address in Røros.

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.