biztrac. BETA
COMPANY REGISTER PROFILE
998234506 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

TIDES AS

Org. no. 998234506 Limited company (AS) Oslo Incorporated 2012 Active
Revenue 2025 NOK 600,000
Operating profit NOK −105,000
Equity NOK −619,000
Incorporated 2012
Share capital NOK 231,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−619k kr).

TIDES AS is registered as a limited company in Oslo, Oslo with organisation number 998234506. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2012. Registered share capital is NOK 231,000, divided into 2309 shares. The company's stated purpose is: “Designe, utvikle og selge egne produkter samt selge designtjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 600,000 in revenue and NOK −105,000 in operating profit.

Former names: HAM DEVELOPMENT AS, HANSSON PRODUCTS AS

Key figures · 2025

Revenue
NOK 600,000
▲ +152 %
Operating profit
NOK −105,000
▲ +71 %
Equity
NOK −619,000
▼ −22 %

Financial health · 2025

Liquidity
35.11
Very good
Current assets ÷ current liabilities
Profitability
-19.7%
Not satisfactory
Return on total assets
Solidity
-129.1%
Weak
Equity as a share of total capital

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

Who owns TIDES AS?

TIDES AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIDES AS

Who owns TIDES AS?

MPH INVEST AS is the largest registered owner, with 47.5%.

What is the revenue of TIDES AS?

TIDES AS had revenue of NOK 600,000 in 2025.

Who is the general manager of TIDES AS?

Mathias Paasche Hansson is registered as general manager of TIDES AS.

Where is TIDES AS based?

TIDES 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.