BIZTRAC BETA
Repair and maintenance of motor vehicles

NOLIK AS

Org. no. 932457938 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 481,000
Operating profit NOK −343,000
Equity NOK −221,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−221k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−343k kr).

NOLIK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932457938. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Sying, restaurering og reparasjon av hjemmemøbler, kjøretøysseter og interiør - kjøp og salg av varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 481,000 in revenue and NOK −343,000 in operating profit.

Key figures · 2024

Revenue
NOK 481,000
Operating profit
NOK −343,000
Equity
NOK −221,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-244.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NOLIK AS?

NAHAL ARIANKIA
NOLIK AS
NOK 481,000 rev. · NOK −343,000 profit

NOLIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOLIK AS

Who owns NOLIK AS?

NAHAL ARIANKIA is the largest registered owner, with 100.0%.

What is the revenue of NOLIK AS?

NOLIK AS had revenue of NOK 481,000 in 2024.

Who is the general manager of NOLIK AS?

Nahal Ariankia is registered as general manager of NOLIK AS.

Where is NOLIK AS based?

NOLIK AS has its business address in Trondheim.

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.