BIZTRAC BETA
General cleaning of buildings

AUTO TEK1 AS

Org. no. 832176192 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK 188,000
Equity NOK 217,000
Incorporated 2023
Employees 6
Share capital NOK 30,000

AUTO TEK1 AS is registered as a limited company in Lørenskog, Akershus with organisation number 832176192. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg av tjenester og produkter knyttet til renhold, vedlikehold og reparasjoner i motorvogner og import og salg av biler og virksomhet som naturlig hører sammen med dette. Videre skal selskapet kunne erverve fast eiendom, og stå for driften av slike.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.9m in revenue and NOK 188,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK 188,000
Equity
NOK 217,000
Est. value
NOK 904,000

Financial health · 2024

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

Who owns AUTO TEK1 AS?

AMIR GORAN
AUTO TEK1 AS
NOK 5.9m rev. · NOK 188,000 profit

AUTO TEK1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUTO TEK1 AS

Who owns AUTO TEK1 AS?

AMIR GORAN is the largest registered owner, with 100.0%.

What is the revenue of AUTO TEK1 AS?

AUTO TEK1 AS had revenue of NOK 5.9m in 2024.

Who is the general manager of AUTO TEK1 AS?

Hiwa Rasulagha Hassan is registered as general manager of AUTO TEK1 AS.

Where is AUTO TEK1 AS based?

AUTO TEK1 AS has its business address in Lørenskog.

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.