BIZTRAC BETA
General cleaning of buildings

MRV BYGG AS

Org. no. 932846454 Limited company (AS) Stange Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 39,000
Equity NOK −151,000
Incorporated 2023
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−151k kr).

MRV BYGG AS is registered as a limited company in Stange, Innlandet with organisation number 932846454. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rengjøring av byggeplasser. Rengjøring av private hjem, kontorer. Flyttevask. Tjenester innen bygge- og anlegg. Bygningsrenovering. Snekkerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 39,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 39,000
Equity
NOK −151,000
Est. value
NOK 322,000

Financial health · 2025

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

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

Who owns MRV BYGG AS?

MONIKA RIMKUVIENE
MRV BYGG AS
NOK 4.5m rev. · NOK 39,000 profit

MRV BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MRV BYGG AS

Who owns MRV BYGG AS?

MONIKA RIMKUVIENE is the largest registered owner, with 100.0%.

What is the revenue of MRV BYGG AS?

MRV BYGG AS had revenue of NOK 4.5m in 2025.

Who is the general manager of MRV BYGG AS?

Monika Rimkuviene is registered as general manager of MRV BYGG AS.

Where is MRV BYGG AS based?

MRV BYGG AS has its business address in Espa.

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.