BIZTRAC BETA
Repair and maintenance of motor vehicles

BIL SERVICE NORD AS

Org. no. 928097420 Limited company (AS) Senja Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 34.4m
Operating profit NOK 3.5m
Equity NOK 4.8m
Incorporated 2021
Employees 28
Share capital NOK 30,000

BIL SERVICE NORD AS is registered as a limited company in Senja, Troms with organisation number 928097420. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2021 and has 28 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bilverksted, herunder reparasjon og vedlikehold på kjøretøy, salg av bildeler og salg/utleie av biler, og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.4m in revenue and NOK 3.5m in operating profit.

Key figures · 2024

Revenue
NOK 34.4m
Operating profit
NOK 3.5m
Equity
NOK 4.8m
Est. value
NOK 15.4m

Financial health · 2024

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

Who owns BIL SERVICE NORD AS?

MARIUS GABRIEL MIGIOIU
BIL SERVICE NORD AS
NOK 34.4m rev. · NOK 3.5m profit

BIL SERVICE NORD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BIL SERVICE NORD AS

Who owns BIL SERVICE NORD AS?

MARIUS GABRIEL MIGIOIU is the largest registered owner, with 80.0%.

What is the revenue of BIL SERVICE NORD AS?

BIL SERVICE NORD AS had revenue of NOK 34.4m in 2024.

Who is the general manager of BIL SERVICE NORD AS?

Morten Linaker is registered as general manager of BIL SERVICE NORD AS.

Where is BIL SERVICE NORD AS based?

BIL SERVICE NORD AS has its business address in Finnsnes.

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.