BIZTRAC BETA
Uoppgitt

A TROLL HOLDING AS

Org. no. 927795256 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −11
Equity NOK 3,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11 kr).

A TROLL HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 927795256. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −11
Equity
NOK 3,000
Est. value
NOK 3,000

Financial health · 2024

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

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

Who owns A TROLL HOLDING AS?

THOMAS WILLIAM ROLLAND-HERSKEDAL
A TROLL HOLDING AS
· NOK −11 profit

A TROLL HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does A TROLL HOLDING AS own?

A TROLL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about A TROLL HOLDING AS

Who owns A TROLL HOLDING AS?

THOMAS WILLIAM ROLLAND-HERSKEDAL is the largest registered owner, with 60.0%.

Who is the general manager of A TROLL HOLDING AS?

Thomas William Rolland-Herskedal is registered as general manager of A TROLL HOLDING AS.

Where is A TROLL HOLDING AS based?

A TROLL HOLDING AS has its business address in Søreidgrend.

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.