BIZTRAC BETA
Repair and maintenance of motor vehicles

IHLE BILVERKSTED AS

Org. no. 985964491 Limited company (AS) Vestre Toten Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK −9,000
Equity NOK 518,000
Incorporated 2003
Share capital NOK 560,000

Signals

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

IHLE BILVERKSTED AS is registered as a limited company in Vestre Toten, Innlandet with organisation number 985964491. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2003. Registered share capital is NOK 560,000, divided into 560 shares. The company's stated purpose is: “Bilverksted, samt annen virksomhet forbundet med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK −9,000
Equity
NOK 518,000
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.8%
Very good
Equity as a share of total capital

Who owns IHLE BILVERKSTED AS?

GEIR HENNING NØKLEBY
IHLE BILVERKSTED AS
NOK 3.6m rev. · NOK −9,000 profit

IHLE BILVERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IHLE BILVERKSTED AS

Who owns IHLE BILVERKSTED AS?

GEIR HENNING NØKLEBY is the largest registered owner, with 100.0%.

What is the revenue of IHLE BILVERKSTED AS?

IHLE BILVERKSTED AS had revenue of NOK 3.6m in 2025.

Who is the general manager of IHLE BILVERKSTED AS?

Geir Henning Nøkleby is registered as general manager of IHLE BILVERKSTED AS.

Where is IHLE BILVERKSTED AS based?

IHLE BILVERKSTED AS has its business address in Bøverbru.

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.