biztrac. BETA
COMPANY REGISTER PROFILE
998509882 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

3T HOLDING AS

Org. no. 998509882 Limited company (AS) Bærum Incorporated 2012 Active
Revenue 2025 NOK 1.9m
Operating profit NOK 1.3m
Equity NOK 52.4m
Incorporated 2012
Share capital NOK 120,000

3T HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 998509882. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 120,000, divided into 100000 shares. The company's stated purpose is: “Holding- og investeringsvirksomhet, herunder investering i alle aktiva klasser, kjøp, salg, utvikling og utleie av eiendommer, deltagelse i andre selskap samt hva som måtte stå i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▼ −89 %
Operating profit
NOK 1.3m
▼ −92 %
Equity
NOK 52.4m
▼ −5 %
Est. value
NOK 37.3m

Financial health · 2025

Liquidity
13.32
Very good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
92.5%
Very good
Equity as a share of total capital

Who owns 3T HOLDING AS?

3T HOLDING AS
NOK 1.9m rev. · NOK 1.3m profit

3T HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does 3T HOLDING AS own?

3T HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about 3T HOLDING AS

Who owns 3T HOLDING AS?

Ellen Kristin Dahl-Pedersen is the largest registered owner, with 100.0%.

What is the revenue of 3T HOLDING AS?

3T HOLDING AS had revenue of NOK 1.9m in 2025.

Where is 3T HOLDING AS based?

3T HOLDING AS has its business address in Lysaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.