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

TRANBY ENTREPRENØR UTLEIE AS

Org. no. 920794459 Limited company (AS) Lier Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 750,000
Equity NOK 598,000
Incorporated 2018
Share capital NOK 300,000

TRANBY ENTREPRENØR UTLEIE AS is registered as a limited company in Lier, Buskerud with organisation number 920794459. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg og utleie av maskiner.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 750,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 750,000
Equity
NOK 598,000
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns TRANBY ENTREPRENØR UTLEIE AS?

STIAN HAUG
TRANBY ENTREPRENØR UTLEIE AS
NOK 5.2m rev. · NOK 750,000 profit

TRANBY ENTREPRENØR UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRANBY ENTREPRENØR UTLEIE AS

Who owns TRANBY ENTREPRENØR UTLEIE AS?

STIAN HAUG is the largest registered owner, with 70.0%.

What is the revenue of TRANBY ENTREPRENØR UTLEIE AS?

TRANBY ENTREPRENØR UTLEIE AS had revenue of NOK 5.2m in 2024.

Who is the general manager of TRANBY ENTREPRENØR UTLEIE AS?

Stian Haug is registered as general manager of TRANBY ENTREPRENØR UTLEIE AS.

Where is TRANBY ENTREPRENØR UTLEIE AS based?

TRANBY ENTREPRENØR UTLEIE AS has its business address in Tranby.

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.