biztrac. BETA
COMPANY REGISTER PROFILE
981289269 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

MILJØ OG GRAVESERVICE AS

Org. no. 981289269 Limited company (AS) Oslo Incorporated 1999 Active
Revenue 2025 NOK 5.5m
Operating profit NOK 80,000
Equity NOK 896,000
Incorporated 1999
Share capital NOK 100,000

MILJØ OG GRAVESERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 981289269. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive som maskinentrepenør, kjøp og salg av varer og tjenester innenfor bygg og anlegg, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 80,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
▼ −10 %
Operating profit
NOK 80,000
▼ −35 %
Equity
NOK 896,000
▲ +6 %
Est. value
NOK 671,000

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
2.6%
Weak
Return on total assets
Solidity
32.7%
Good
Equity as a share of total capital

Who owns MILJØ OG GRAVESERVICE AS?

MILJØ OG GRAVESERVICE AS
NOK 5.5m rev. · NOK 80,000 profit

MILJØ OG GRAVESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILJØ OG GRAVESERVICE AS

Who owns MILJØ OG GRAVESERVICE AS?

Øyvind Meidel is the largest registered owner, with 100.0%.

What is the revenue of MILJØ OG GRAVESERVICE AS?

MILJØ OG GRAVESERVICE AS had revenue of NOK 5.5m in 2025.

Who is the general manager of MILJØ OG GRAVESERVICE AS?

Øyvind Meidel is registered as general manager of MILJØ OG GRAVESERVICE AS.

Where is MILJØ OG GRAVESERVICE AS based?

MILJØ OG GRAVESERVICE AS has its business address in Oslo.

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.