BIZTRAC BETA
Computer consultancy and computer facilities management activities

TIDI AS

Org. no. 933133893 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 47,000
Operating profit NOK −19,000
Equity NOK 27,000
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

TIDI AS is registered as a limited company in Oslo, Oslo with organisation number 933133893. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 47,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 47,000
Operating profit
NOK −19,000
Equity
NOK 27,000
Est. value
NOK 91,000

Financial health · 2025

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

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

Who owns TIDI AS?

SVELLE AS
TIDI AS
NOK 47,000 rev. · NOK −19,000 profit

TIDI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIDI AS

Who owns TIDI AS?

SVELLE AS is the largest registered owner, with 60.0%.

What is the revenue of TIDI AS?

TIDI AS had revenue of NOK 47,000 in 2025.

Who is the general manager of TIDI AS?

Helene Svelle is registered as general manager of TIDI AS.

Where is TIDI AS based?

TIDI 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.