BIZTRAC BETA
Other content distribution activities

TANGO DATASENTER OG EIENDOM AS

Org. no. 932540819 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 215,000
Operating profit NOK 215,000
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

TANGO DATASENTER OG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 932540819. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie og drifte datasenter for hostingtjenester og utvinning av kryptovaluta samt eie eiendom og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 215,000 in revenue and NOK 215,000 in operating profit.

Key figures · 2024

Revenue
NOK 215,000
Operating profit
NOK 215,000
Equity
NOK 30,000
Est. value
NOK 722,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TANGO DATASENTER OG EIENDOM AS?

EIENDOMSDRIFT 2 AS
TANGO DATASENTER OG EIENDOM AS
NOK 215,000 rev. · NOK 215,000 profit

TANGO DATASENTER OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TANGO DATASENTER OG EIENDOM AS

Who owns TANGO DATASENTER OG EIENDOM AS?

EIENDOMSDRIFT 2 AS is the largest registered owner, with 100.0%.

What is the revenue of TANGO DATASENTER OG EIENDOM AS?

TANGO DATASENTER OG EIENDOM AS had revenue of NOK 215,000 in 2024.

Where is TANGO DATASENTER OG EIENDOM AS based?

TANGO DATASENTER OG EIENDOM AS has its business address in Oslo.

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.