BIZTRAC BETA
Uoppgitt

TRIKANTEN HOLDING AS

Org. no. 935840996 Limited company (AS) Verdal Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −97,000
Equity NOK 645,000
Incorporated 2025
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−97k kr).

TRIKANTEN HOLDING AS is registered as a limited company in Verdal, Trøndelag with organisation number 935840996. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 33,000, divided into 30000 shares. The company's stated purpose is: “Investeringer, aksjer og verdipapirer, samt det som naturlig står i forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −97,000
Equity
NOK 645,000
Est. value
NOK 758,000

Financial health · 2025

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

Who owns TRIKANTEN HOLDING AS?

ANNA-LENA LØBAKK
TRIKANTEN HOLDING AS
· NOK −97,000 profit

TRIKANTEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TRIKANTEN HOLDING AS own?

TRIKANTEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TRIKANTEN HOLDING AS

Who owns TRIKANTEN HOLDING AS?

ANNA-LENA LØBAKK is the largest registered owner, with 50.0%.

Who is the general manager of TRIKANTEN HOLDING AS?

Agnar Løbakk is registered as general manager of TRIKANTEN HOLDING AS.

Where is TRIKANTEN HOLDING AS based?

TRIKANTEN HOLDING AS has its business address in Verdal.

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.