BIZTRAC BETA
Site preparation

BERG GRAVING & TRANSPORT AS

Org. no. 929045963 Limited company (AS) Målselv Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 610,000
Equity NOK 400,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

BERG GRAVING & TRANSPORT AS is registered as a limited company in Målselv, Troms with organisation number 929045963. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Bygg og anleggs entreprenør, skogtjenester, transport.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 610,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 610,000
Equity
NOK 400,000
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns BERG GRAVING & TRANSPORT AS?

MARTIN BERG
BERG GRAVING & TRANSPORT AS
NOK 9.9m rev. · NOK 610,000 profit

BERG GRAVING & TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERG GRAVING & TRANSPORT AS

Who owns BERG GRAVING & TRANSPORT AS?

MARTIN BERG is the largest registered owner, with 100.0%.

What is the revenue of BERG GRAVING & TRANSPORT AS?

BERG GRAVING & TRANSPORT AS had revenue of NOK 9.9m in 2024.

Who is the general manager of BERG GRAVING & TRANSPORT AS?

Martin Berg is registered as general manager of BERG GRAVING & TRANSPORT AS.

Where is BERG GRAVING & TRANSPORT AS based?

BERG GRAVING & TRANSPORT AS has its business address in Bardufoss.

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.