BIZTRAC BETA
Repair and maintenance of motor vehicles

AUTO FIRE AS

Org. no. 947631055 Limited company (AS) Steinkjer Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 27.1m
Operating profit NOK −421,000
Equity NOK 2.9m
Incorporated 1988
Employees 10
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−421k kr).

AUTO FIRE AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 947631055. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1988 and has 10 registered employees. Registered share capital is NOK 500,000, divided into 400 shares. The company's stated purpose is: “Å drive salg av nye og brukte biler, reservedeler m.v., drift av verksted og hva dermed står i forbindelse og herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.1m in revenue and NOK −421,000 in operating profit.

Key figures · 2024

Revenue
NOK 27.1m
Operating profit
NOK −421,000
Equity
NOK 2.9m
Est. value
NOK 19.9m

Financial health · 2024

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

Who owns AUTO FIRE AS?

BILCENTRUM AS
AUTO FIRE AS
NOK 27.1m rev. · NOK −421,000 profit

AUTO FIRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUTO FIRE AS

Who owns AUTO FIRE AS?

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

What is the revenue of AUTO FIRE AS?

AUTO FIRE AS had revenue of NOK 27.1m in 2024.

Who is the general manager of AUTO FIRE AS?

Edvard Slapgaard is registered as general manager of AUTO FIRE AS.

Where is AUTO FIRE AS based?

AUTO FIRE AS has its business address in Steinkjer.

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.