BIZTRAC BETA
Rental and operating of own or leased real estate

TJUVHOLMEN EIENDOM HOLDING AS

Org. no. 921968698 Limited company (AS) Færder Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 548,000
Incorporated 2018
Share capital NOK 70,000

Signals

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

TJUVHOLMEN EIENDOM HOLDING AS is registered as a limited company in Færder, Vestfold with organisation number 921968698. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 70,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, eiendom, løsøre og hva dermed står i forbindelse, direkte eller via deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 548,000
Est. value
NOK 500,000

Financial health · 2024

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

Who owns TJUVHOLMEN EIENDOM HOLDING AS?

GLENN EINAR EDVARDSEN
TJUVHOLMEN EIENDOM HOLDING AS
NOK 0 rev. · NOK −16,000 profit

TJUVHOLMEN EIENDOM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TJUVHOLMEN EIENDOM HOLDING AS

Who owns TJUVHOLMEN EIENDOM HOLDING AS?

GLENN EINAR EDVARDSEN is the largest registered owner, with 50.0%.

What is the revenue of TJUVHOLMEN EIENDOM HOLDING AS?

TJUVHOLMEN EIENDOM HOLDING AS had revenue of NOK 0 in 2024.

Where is TJUVHOLMEN EIENDOM HOLDING AS based?

TJUVHOLMEN EIENDOM HOLDING AS has its business address in Duken.

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.