BIZTRAC BETA
Rental and operating of own or leased real estate

TEP HOLDING AS

Org. no. 888977112 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 102,000
Operating profit NOK −604,000
Equity NOK 6.7m
Incorporated 2005
Share capital NOK 174,000

Signals

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

TEP HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 888977112. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 174,000, divided into 2050 shares. The company's stated purpose is: “Eie og utleie av fast eiendom, handel i tilknytning til dette, delta i andre selskaper og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 102,000 in revenue and NOK −604,000 in operating profit.

Key figures · 2024

Revenue
NOK 102,000
Operating profit
NOK −604,000
Equity
NOK 6.7m
Est. value
NOK 11.6m

Financial health · 2024

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

Who owns TEP HOLDING AS?

TOM ERIK PEDERSEN
TEP HOLDING AS
NOK 102,000 rev. · NOK −604,000 profit

TEP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEP HOLDING AS own?

TEP HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about TEP HOLDING AS

Who owns TEP HOLDING AS?

TOM ERIK PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TEP HOLDING AS?

TEP HOLDING AS had revenue of NOK 102,000 in 2024.

Where is TEP HOLDING AS based?

TEP HOLDING AS has its business address in Hamresanden.

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.