BIZTRAC BETA
Repair and maintenance of motor vehicles

ADSERØ BILVERKSTED AS

Org. no. 914526698 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 13.5m
Operating profit NOK 306,000
Equity NOK 1.5m
Incorporated 2014
Employees 13
Share capital NOK 600,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

ADSERØ BILVERKSTED AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914526698. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2014 and has 13 registered employees. Registered share capital is NOK 600,000, divided into 6000 shares. The company's stated purpose is: “Bilverksted for mekaniske tjenester på bil samt bilpleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.5m in revenue and NOK 306,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.5m
Operating profit
NOK 306,000
Equity
NOK 1.5m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns ADSERØ BILVERKSTED AS?

KEIV AS
ADSERØ BILVERKSTED AS
NOK 13.5m rev. · NOK 306,000 profit

ADSERØ BILVERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADSERØ BILVERKSTED AS

Who owns ADSERØ BILVERKSTED AS?

KEIV AS is the largest registered owner, with 100.0%.

What is the revenue of ADSERØ BILVERKSTED AS?

ADSERØ BILVERKSTED AS had revenue of NOK 13.5m in 2024.

Where is ADSERØ BILVERKSTED AS based?

ADSERØ BILVERKSTED AS has its business address in Ranheim.

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.