BIZTRAC BETA
Rental and operating of own or leased real estate

TEAM EIENDOM AS

Org. no. 981957377 Limited company (AS) Drammen Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 102,000
Operating profit NOK −65
Equity NOK 1.8m
Incorporated 2000
Share capital NOK 100,000

Signals

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

TEAM EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 981957377. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investeringsvirksomhet, utvikling, kjøp, salg og drift av fast eiendom, samt ved kjøp av aksjer eller på annen måte delta i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 102,000 in revenue and NOK −65 in operating profit.

Key figures · 2024

Revenue
NOK 102,000
Operating profit
NOK −65
Equity
NOK 1.8m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns TEAM EIENDOM AS?

HEGE GYLLSTRØM
TEAM EIENDOM AS
NOK 102,000 rev. · NOK −65 profit

TEAM EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEAM EIENDOM AS

Who owns TEAM EIENDOM AS?

HEGE GYLLSTRØM is the largest registered owner, with 25.0%.

What is the revenue of TEAM EIENDOM AS?

TEAM EIENDOM AS had revenue of NOK 102,000 in 2024.

Who is the general manager of TEAM EIENDOM AS?

Hege Gyllstrøm is registered as general manager of TEAM EIENDOM AS.

Where is TEAM EIENDOM AS based?

TEAM EIENDOM AS has its business address in Drammen.

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.