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

SØRBY UTLEIE AS

Org. no. 888422552 Limited company (AS) Indre Østfold Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 262.0m
Operating profit NOK 40.9m
Equity NOK 28.9m
Incorporated 2005
Employees 77
Share capital NOK 100,000

SØRBY UTLEIE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 888422552. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2005 and has 77 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av maskiner og utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 262.0m in revenue and NOK 40.9m in operating profit.

Key figures · 2024

Revenue
NOK 262.0m
Operating profit
NOK 40.9m
Equity
NOK 28.9m
Est. value
NOK 121.4m

Financial health · 2025

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

Who owns SØRBY UTLEIE AS?

SØRBY HOLDING AS
SØRBY UTLEIE AS
NOK 262.0m rev. · NOK 40.9m profit

SØRBY UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SØRBY UTLEIE AS er morselskap for 5 datterselskaper:

Frequently asked questions about SØRBY UTLEIE AS

Who owns SØRBY UTLEIE AS?

SØRBY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SØRBY UTLEIE AS?

SØRBY UTLEIE AS had revenue of NOK 262.0m in 2024.

Who is the general manager of SØRBY UTLEIE AS?

Martin Authen is registered as general manager of SØRBY UTLEIE AS.

Where is SØRBY UTLEIE AS based?

SØRBY UTLEIE AS has its business address in Tomter.

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.