BIZTRAC BETA
Repair and maintenance of motor vehicles

AUTORENT VERKSTED AS

Org. no. 926909363 Limited company (AS) Svalbard Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 1.2m
Equity NOK 1.5m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AUTORENT VERKSTED AS is registered as a limited company in Svalbard, Svalbard with organisation number 926909363. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bilverksted og andre oppgaver som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 1.2m
Equity
NOK 1.5m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns AUTORENT VERKSTED AS?

FJO HOLDING AS
AUTORENT VERKSTED AS
NOK 6.8m rev. · NOK 1.2m profit

AUTORENT VERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUTORENT VERKSTED AS

Who owns AUTORENT VERKSTED AS?

FJO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AUTORENT VERKSTED AS?

AUTORENT VERKSTED AS had revenue of NOK 6.8m in 2024.

Who is the general manager of AUTORENT VERKSTED AS?

Frank Johnny Olsen is registered as general manager of AUTORENT VERKSTED AS.

Where is AUTORENT VERKSTED AS based?

AUTORENT VERKSTED AS has its business address in Longyearbyen.

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.