BIZTRAC BETA
Rental and operating of own or leased real estate

TJF HOLDING AS

Org. no. 928904164 Limited company (AS) Hole Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2.7m
Equity NOK 200.7m
Incorporated 2021
Share capital NOK 159,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,7 mill kr).

TJF HOLDING AS is registered as a limited company in Hole, Buskerud with organisation number 928904164. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 159,000, divided into 100 shares. The company's stated purpose is: “Handel samt kjøp og salg av aksjer, fast eiendom og andre verdier som styret måtte beslutte, drift og utvikling av eiendom, og deltagelse i andre foretagender av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2.7m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2.7m
Equity
NOK 200.7m
Est. value
NOK 149.6m

Financial health · 2024

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

Who owns TJF HOLDING AS?

TORE JOHAN FLOBERG
TJF HOLDING AS
NOK 0 rev. · NOK −2.7m profit

TJF HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TJF HOLDING AS own?

TJF HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about TJF HOLDING AS

Who owns TJF HOLDING AS?

TORE JOHAN FLOBERG is the largest registered owner, with 100.0%.

What is the revenue of TJF HOLDING AS?

TJF HOLDING AS had revenue of NOK 0 in 2024.

Where is TJF HOLDING AS based?

TJF HOLDING AS has its business address in Sollihøgda.

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.