BIZTRAC BETA
Site preparation

MODUM GRAVING OG TRANSPORT AS

Org. no. 930939986 Limited company (AS) Modum Incorporated 2023 Active
Ownership graph ↗
Revenue 2023 NOK 2.1m
Operating profit NOK 606,000
Equity NOK 498,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-22 Under avvikling registrert 2026-06-22.

MODUM GRAVING OG TRANSPORT AS is registered as a limited company in Modum, Buskerud with organisation number 930939986. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Graving, sprenging, terreng og grunnarbeider, transport, herunder entreprenørvirksomhet, utleie.”. The most recent filed accounts, for the 2023 financial year, show NOK 2.1m in revenue and NOK 606,000 in operating profit.

Key figures · 2023

Revenue
NOK 2.1m
Operating profit
NOK 606,000
Equity
NOK 498,000
Est. value
NOK 2.0m

Financial health · 2023

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

Who owns MODUM GRAVING OG TRANSPORT AS?

No shareholders are registered for MODUM GRAVING OG TRANSPORT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MODUM GRAVING OG TRANSPORT AS

What is the revenue of MODUM GRAVING OG TRANSPORT AS?

MODUM GRAVING OG TRANSPORT AS had revenue of NOK 2.1m in 2023.

Who is the general manager of MODUM GRAVING OG TRANSPORT AS?

Steffen Engelhart Brekke is registered as general manager of MODUM GRAVING OG TRANSPORT AS.

Where is MODUM GRAVING OG TRANSPORT AS based?

MODUM GRAVING OG TRANSPORT AS has its business address in Åmot.

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.