BIZTRAC BETA
Sound recording and music publishing activities

RISING TIDE AS

Org. no. 991937455 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −410,000
Equity NOK 7.0m
Incorporated 2007
Share capital NOK 100,000

Signals

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

RISING TIDE AS is registered as a limited company in Oslo, Oslo with organisation number 991937455. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Musikkproduksjon og underholdning innen musikk, samt forretningsvirksomhet knyttet til dette. Selskapet skal også kunne drive med investering og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −410,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −410,000
Equity
NOK 7.0m
Est. value
NOK 12.7m

Financial health · 2024

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

Who owns RISING TIDE AS?

HÅVARD MATHIESEN
RISING TIDE AS
NOK 0 rev. · NOK −410,000 profit

RISING TIDE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RISING TIDE AS own?

RISING TIDE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about RISING TIDE AS

Who owns RISING TIDE AS?

HÅVARD MATHIESEN is the largest registered owner, with 100.0%.

What is the revenue of RISING TIDE AS?

RISING TIDE AS had revenue of NOK 0 in 2024.

Where is RISING TIDE AS based?

RISING TIDE 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.