BIZTRAC BETA
Site preparation

MIR GRAVE OG DRENERING AS

Org. no. 934365305 Limited company (AS) Lier Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 52,000
Equity NOK 66,000
Incorporated 2024
Share capital NOK 30,000

MIR GRAVE OG DRENERING AS is registered as a limited company in Lier, Buskerud with organisation number 934365305. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Grave, grunnarbeid og drenering samt andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 52,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 52,000
Equity
NOK 66,000
Est. value
NOK 230,000

Financial health · 2025

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.0%
Weak
Equity as a share of total capital

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

Who owns MIR GRAVE OG DRENERING AS?

AOWS AKREI
MIR GRAVE OG DRENERING AS
NOK 1.7m rev. · NOK 52,000 profit

MIR GRAVE OG DRENERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIR GRAVE OG DRENERING AS

Who owns MIR GRAVE OG DRENERING AS?

AOWS AKREI is the largest registered owner, with 100.0%.

What is the revenue of MIR GRAVE OG DRENERING AS?

MIR GRAVE OG DRENERING AS had revenue of NOK 1.7m in 2025.

Who is the general manager of MIR GRAVE OG DRENERING AS?

Aows Akrei is registered as general manager of MIR GRAVE OG DRENERING AS.

Where is MIR GRAVE OG DRENERING AS based?

MIR GRAVE OG DRENERING AS has its business address in Gullaug.

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.