BIZTRAC BETA
Other captive investment companies

TAGHOLDT AS

Org. no. 999102050 Limited company (AS) Grimstad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 78,000
Operating profit NOK −489,000
Equity NOK 3.6m
Incorporated 2012
Share capital NOK 100,000

Signals

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

TAGHOLDT AS is registered as a limited company in Grimstad, Agder with organisation number 999102050. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Investering i aksjer og eiendom, annen tjenesteyting samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 78,000 in revenue and NOK −489,000 in operating profit.

Key figures · 2025

Revenue
NOK 78,000
Operating profit
NOK −489,000
Equity
NOK 3.6m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns TAGHOLDT AS?

EINAR MOEN
TAGHOLDT AS
NOK 78,000 rev. · NOK −489,000 profit

TAGHOLDT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TAGHOLDT AS own?

TAGHOLDT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TAGHOLDT AS

Who owns TAGHOLDT AS?

EINAR MOEN is the largest registered owner, with 100.0%.

What is the revenue of TAGHOLDT AS?

TAGHOLDT AS had revenue of NOK 78,000 in 2025.

Who is the general manager of TAGHOLDT AS?

Einar Moen is registered as general manager of TAGHOLDT AS.

Where is TAGHOLDT AS based?

TAGHOLDT AS has its business address in Grimstad.

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.