BIZTRAC BETA
Retail sale of motor vehicle parts and accessories

TRIC AS

Org. no. 925740608 Limited company (AS) Ullensaker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 55,000
Operating profit NOK 7,000
Equity NOK −359
Incorporated 2020
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−359 kr).
  • Nylig endring 2026-04-20 Adresseendring registrert 2026-04-20.

TRIC AS is registered as a limited company in Ullensaker, Akershus with organisation number 925740608. The business is classified under retail sale of motor vehicle parts and accessories (NACE 47.820). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Import og salg av elektriske kjøretøy og tilbehør til slike produkter, og andre produkter som naturlig sammenfaller med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 55,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2024

Revenue
NOK 55,000
Operating profit
NOK 7,000
Equity
NOK −359
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns TRIC AS?

NIELVE AS
TRIC AS
NOK 55,000 rev. · NOK 7,000 profit

TRIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRIC AS

Who owns TRIC AS?

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

What is the revenue of TRIC AS?

TRIC AS had revenue of NOK 55,000 in 2024.

Who is the general manager of TRIC AS?

Luana-Maria Lupsa is registered as general manager of TRIC AS.

Where is TRIC AS based?

TRIC AS has its business address in Gardermoen.

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.