BIZTRAC BETA
Business and other management consultancy activities

TIDE RENEWABLES AS

Org. no. 935036275 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −39,000
Equity NOK 5.0m
Incorporated 2024
Share capital NOK 50,000

Signals

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

TIDE RENEWABLES AS is registered as a limited company in Oslo, Oslo with organisation number 935036275. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Utvikle prosjekter innen fornybar energi, deltakelse i andre selskaper, konsulenttjenester og hva som ellers står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −39,000
Equity
NOK 5.0m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns TIDE RENEWABLES AS?

BROSME AS
TIDE RENEWABLES AS
NOK 1.1m rev. · NOK −39,000 profit

TIDE RENEWABLES AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIDE RENEWABLES AS

Who owns TIDE RENEWABLES AS?

BROSME AS is the largest registered owner, with 20.0%.

What is the revenue of TIDE RENEWABLES AS?

TIDE RENEWABLES AS had revenue of NOK 1.1m in 2025.

Who is the general manager of TIDE RENEWABLES AS?

Shun Wei Gong is registered as general manager of TIDE RENEWABLES AS.

Where is TIDE RENEWABLES AS based?

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