BIZTRAC BETA
Rental and operating of own or leased real estate

TESS SØR EIENDOM AS

Org. no. 957002307 Limited company (AS) Lier Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 784,000
Operating profit NOK 375,000
Equity NOK 5.6m
Incorporated 1990
Share capital NOK 2.7m

TESS SØR EIENDOM AS is registered as a limited company in Lier, Buskerud with organisation number 957002307. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 2.7m, divided into 27000 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 784,000 in revenue and NOK 375,000 in operating profit.

Key figures · 2024

Revenue
NOK 784,000
Operating profit
NOK 375,000
Equity
NOK 5.6m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns TESS SØR EIENDOM AS?

TESS EIENDOM AS
TESS SØR EIENDOM AS
NOK 784,000 rev. · NOK 375,000 profit

TESS SØR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TESS SØR EIENDOM AS own?

TESS SØR EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TESS SØR EIENDOM AS

Who owns TESS SØR EIENDOM AS?

TESS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of TESS SØR EIENDOM AS?

TESS SØR EIENDOM AS had revenue of NOK 784,000 in 2024.

Who is the general manager of TESS SØR EIENDOM AS?

Jan Ivar Moe Lindseth is registered as general manager of TESS SØR EIENDOM AS.

Where is TESS SØR EIENDOM AS based?

TESS SØR EIENDOM AS has its business address in Lierstranda.

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.