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

UTLEIE1 AS

Org. no. 920626866 Limited company (AS) Tønsberg Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 706,000
Equity NOK 736,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

UTLEIE1 AS is registered as a limited company in Tønsberg, Vestfold with organisation number 920626866. 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 30,000, divided into 30 shares. The company's stated purpose is: “Å drive kjøp,salg og utleie av maskiner, utstyr og eiendom samt hva som hører under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 706,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 706,000
Equity
NOK 736,000
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.5%
Good
Equity as a share of total capital

Who owns UTLEIE1 AS?

PN HOLDING AS
UTLEIE1 AS
NOK 1.3m rev. · NOK 706,000 profit

UTLEIE1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UTLEIE1 AS

Who owns UTLEIE1 AS?

PN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of UTLEIE1 AS?

UTLEIE1 AS had revenue of NOK 1.3m in 2025.

Who is the general manager of UTLEIE1 AS?

Pål Nyegaard is registered as general manager of UTLEIE1 AS.

Where is UTLEIE1 AS based?

UTLEIE1 AS has its business address in Tolvsrød.

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.