BIZTRAC BETA
Non-specialised wholesale of food, beverages and tobacco

MG FOODS AS

Org. no. 817586112 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK −134,000
Equity NOK −2.3m
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−134k kr).

MG FOODS AS is registered as a limited company in Bergen, Vestland with organisation number 817586112. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Import og handel av matvarer, drikkevarer og andre typer varer og alt som naturlig hører inn under dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK −134,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK −134,000
Equity
NOK −2.3m

Financial health · 2024

Liquidity
2.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-68.1%
Weak
Equity as a share of total capital

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

Who owns MG FOODS AS?

TIM INVEST HOLDING AS
MG FOODS AS
NOK 10.7m rev. · NOK −134,000 profit

MG FOODS AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about MG FOODS AS

Who owns MG FOODS AS?

TIM INVEST HOLDING AS is the largest registered owner, with 20.0%.

What is the revenue of MG FOODS AS?

MG FOODS AS had revenue of NOK 10.7m in 2024.

Where is MG FOODS AS based?

MG FOODS AS has its business address in Blomsterdalen.

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.