biztrac. BETA
COMPANY REGISTER PROFILE
932684470 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of construction and civil engineering machinery and equipment

IE UTSTYR AS

Org. no. 932684470 Limited company (AS) Vestby Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 309,000
Operating profit NOK 76,000
Equity NOK 41,000
Incorporated 2023
Share capital NOK 30,000

IE UTSTYR AS is registered as a limited company in Vestby, Akershus with organisation number 932684470. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleie av utstyr og annet.”. The most recent filed accounts, for the 2025 financial year, show NOK 309,000 in revenue and NOK 76,000 in operating profit.

Key figures · 2025

Revenue
NOK 309,000
▲ +3 %
Operating profit
NOK 76,000
▲ +36 %
Equity
NOK 41,000
▲ +27 %
Est. value
NOK 209,000

Financial health · 2025

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
15.7%
Very good
Return on total assets
Solidity
9.1%
Weak
Equity as a share of total capital

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

Who owns IE UTSTYR AS?

IE UTSTYR AS
NOK 309,000 rev. · NOK 76,000 profit

IE UTSTYR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about IE UTSTYR AS

Who owns IE UTSTYR AS?

Ivan Jacobsen is the largest registered owner, with 50.0%.

What is the revenue of IE UTSTYR AS?

IE UTSTYR AS had revenue of NOK 309,000 in 2025.

Who is the general manager of IE UTSTYR AS?

Elisabeth Bottengård Aune is registered as general manager of IE UTSTYR AS.

Where is IE UTSTYR AS based?

IE UTSTYR AS has its business address in Vestby.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.