BIZTRAC BETA
Repair and maintenance of motor vehicles

INTAKT BILSKADE MO I RANA AS

Org. no. 971644915 Limited company (AS) Rana Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 28.8m
Operating profit NOK 1.5m
Equity NOK 3.2m
Incorporated 1995
Employees 17
Share capital NOK 111,000

INTAKT BILSKADE MO I RANA AS is registered as a limited company in Rana, Nordland with organisation number 971644915. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1995 and has 17 registered employees. Registered share capital is NOK 111,000, divided into 555 shares. The company's stated purpose is: “Vedlikehold og reparasjon av motorvogner. ”. The most recent filed accounts, for the 2024 financial year, show NOK 28.8m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 28.8m
Operating profit
NOK 1.5m
Equity
NOK 3.2m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns INTAKT BILSKADE MO I RANA AS?

INTAKT NORD AS
INTAKT BILSKADE MO I RANA AS
NOK 28.8m rev. · NOK 1.5m profit

INTAKT BILSKADE MO I RANA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about INTAKT BILSKADE MO I RANA AS

Who owns INTAKT BILSKADE MO I RANA AS?

INTAKT NORD AS is the largest registered owner, with 50.1%.

What is the revenue of INTAKT BILSKADE MO I RANA AS?

INTAKT BILSKADE MO I RANA AS had revenue of NOK 28.8m in 2024.

Who is the general manager of INTAKT BILSKADE MO I RANA AS?

Karl Erik Grønli is registered as general manager of INTAKT BILSKADE MO I RANA AS.

Where is INTAKT BILSKADE MO I RANA AS based?

INTAKT BILSKADE MO I RANA AS has its business address in Mo I Rana.

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.