BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

BERGSTRØM UTLEIE AS

Org. no. 934997425 Limited company (AS) Skien Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK −48,000
Equity NOK 6,000
Incorporated 2025
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−48k kr).

BERGSTRØM UTLEIE AS is registered as a limited company in Skien, Telemark with organisation number 934997425. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Tilby utleie av bygg- og anleggsmaskiner, forskjellige typer maskiner, utstyr og verktøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK −48,000 in operating profit.

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK −48,000
Equity
NOK 6,000
Est. value
NOK 7,000

Financial health · 2025

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

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

Who owns BERGSTRØM UTLEIE AS?

TOMMY LANGERØD BERGSTRØM
BERGSTRØM UTLEIE AS
NOK 7,000 rev. · NOK −48,000 profit

BERGSTRØM UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGSTRØM UTLEIE AS

Who owns BERGSTRØM UTLEIE AS?

TOMMY LANGERØD BERGSTRØM is the largest registered owner, with 50.0%.

What is the revenue of BERGSTRØM UTLEIE AS?

BERGSTRØM UTLEIE AS had revenue of NOK 7,000 in 2025.

Where is BERGSTRØM UTLEIE AS based?

BERGSTRØM UTLEIE AS has its business address in Skien.

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.