biztrac. BETA
COMPANY REGISTER PROFILE
935767520 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Production of meat and poultry meat products

MATFOREDLING AS

Org. no. 935767520 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 4,000
Equity NOK 27,000
Incorporated 2025
Employees 5
Share capital NOK 30,000

MATFOREDLING AS is registered as a limited company in Bærum, Akershus with organisation number 935767520. The business is classified under production of meat and poultry meat products (NACE 10.130). The company was incorporated in 2025 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produsere kjøttvarer (pølser, spekemat og pålegg) med eksepsjonell smak og av høy kvaliet, uten kunstige tilsetningsstoff.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 4,000
Equity
NOK 27,000
Est. value
NOK 31,000

Financial health · 2025

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

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

Who owns MATFOREDLING AS?

MATFOREDLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MATFOREDLING AS

Who owns MATFOREDLING AS?

Magnus Thorvik is the largest registered owner, with 75.0%.

What is the revenue of MATFOREDLING AS?

MATFOREDLING AS had revenue of NOK 1.2m in 2025.

Who is the general manager of MATFOREDLING AS?

Magnus Thorvik is registered as general manager of MATFOREDLING AS.

Where is MATFOREDLING AS based?

MATFOREDLING AS has its business address in Stabekk.

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.