BIZTRAC BETA
Freight transport by road

MRG INVEST AS

Org. no. 998491398 Limited company (AS) Hole Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 297,000
Operating profit NOK −39,000
Equity NOK 448,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−39k kr).

MRG INVEST AS is registered as a limited company in Hole, Buskerud with organisation number 998491398. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Godstransport på vei, leie- og utleie av arbeidskraft, vikartjenester, leie- og utleie av biler, konsulenttjenester, samt import og salg av biler. Selskapet kan også delta i andre selskaper med økonomisk interesse.”. The most recent filed accounts, for the 2025 financial year, show NOK 297,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 297,000
Operating profit
NOK −39,000
Equity
NOK 448,000
Est. value
NOK 368,000

Financial health · 2025

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

Who owns MRG INVEST AS?

RUNAR GULBRANDSEN
MRG INVEST AS
NOK 297,000 rev. · NOK −39,000 profit

MRG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MRG INVEST AS

Who owns MRG INVEST AS?

RUNAR GULBRANDSEN is the largest registered owner, with 100.0%.

What is the revenue of MRG INVEST AS?

MRG INVEST AS had revenue of NOK 297,000 in 2025.

Who is the general manager of MRG INVEST AS?

Runar Gulbrandsen is registered as general manager of MRG INVEST AS.

Where is MRG INVEST AS based?

MRG INVEST AS has its business address in Røyse.

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.