BIZTRAC BETA
Rental and operating of own or leased real estate

TIT HOLDING AS

Org. no. 897964732 Limited company (AS) Flesberg Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 1.3m
Equity NOK 19.5m
Incorporated 2012
Share capital NOK 30,000

TIT HOLDING AS is registered as a limited company in Flesberg, Buskerud with organisation number 897964732. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Sleskapets virksomhet er kjøp og salg av aksjer, andre selskapsandeler, kapital-/handelsvarer, håndverkervirksomhet samt kjøp, salg, utvikling, forvaltning og utleie av fast eiendom. Selskapet skal videre ha anledning til å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 1.3m
Equity
NOK 19.5m
Est. value
NOK 17.9m

Financial health · 2025

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

Who owns TIT HOLDING AS?

ROGER RUSTAND
TIT HOLDING AS
NOK 5.0m rev. · NOK 1.3m profit

TIT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIT HOLDING AS own?

TIT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TIT HOLDING AS

Who owns TIT HOLDING AS?

ROGER RUSTAND is the largest registered owner, with 100.0%.

What is the revenue of TIT HOLDING AS?

TIT HOLDING AS had revenue of NOK 5.0m in 2025.

Where is TIT HOLDING AS based?

TIT HOLDING AS has its business address in Lampeland.

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.