BIZTRAC BETA
Rental and operating of own or leased real estate

TOTAL TEAM EIENDOM AS

Org. no. 986611495 Limited company (AS) Arendal Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 903,000
Operating profit NOK 400,000
Equity NOK 477,000
Incorporated 2004
Share capital NOK 111,000

TOTAL TEAM EIENDOM AS is registered as a limited company in Arendal, Agder with organisation number 986611495. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 111,000, divided into 1110 shares. The company's stated purpose is: “Utleie av fast eiendom samt hva som naturlig hører sammen med dette. Selskapet kan også eie andeler i øvrige selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 903,000 in revenue and NOK 400,000 in operating profit.

Key figures · 2025

Revenue
NOK 903,000
Operating profit
NOK 400,000
Equity
NOK 477,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.7%
Satisfactory
Equity as a share of total capital

Who owns TOTAL TEAM EIENDOM AS?

JAN ARILD JOHANNESEN
TOTAL TEAM EIENDOM AS
NOK 903,000 rev. · NOK 400,000 profit

TOTAL TEAM EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does TOTAL TEAM EIENDOM AS own?

TOTAL TEAM EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TOTAL TEAM EIENDOM AS

Who owns TOTAL TEAM EIENDOM AS?

JAN ARILD JOHANNESEN is the largest registered owner, with 39.7%.

What is the revenue of TOTAL TEAM EIENDOM AS?

TOTAL TEAM EIENDOM AS had revenue of NOK 903,000 in 2025.

Where is TOTAL TEAM EIENDOM AS based?

TOTAL TEAM EIENDOM AS has its business address in Arendal.

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.