BIZTRAC BETA
Construction of residential and non-residential buildings

WELLCO EIENDOM AS

Org. no. 984642938 Limited company (AS) Sandnes Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 3.1m
Equity NOK 31.8m
Incorporated 2002
Share capital NOK 200,000

WELLCO EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 984642938. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Investeringsselskap, hovedsaklig å eie eiendommer, aksjer, med videre.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 3.1m
Equity
NOK 31.8m
Est. value
NOK 22.7m

Financial health · 2024

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

Who owns WELLCO EIENDOM AS?

TST INVEST AS
WELLCO EIENDOM AS
NOK 5.8m rev. · NOK 3.1m profit

WELLCO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WELLCO EIENDOM AS own?

WELLCO EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WELLCO EIENDOM AS

Who owns WELLCO EIENDOM AS?

TST INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of WELLCO EIENDOM AS?

WELLCO EIENDOM AS had revenue of NOK 5.8m in 2024.

Who is the general manager of WELLCO EIENDOM AS?

Tor Øistein Torgersen is registered as general manager of WELLCO EIENDOM AS.

Where is WELLCO EIENDOM AS based?

WELLCO EIENDOM AS has its business address in Sandnes.

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.