BIZTRAC BETA
Activities of tour guides

NORTHRIDE AS

Org. no. 936474578 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −610
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−610 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-20.

NORTHRIDE AS is registered as a limited company in Tromsø, Troms with organisation number 936474578. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby guide- og reiseledertjenester, herunder, men ikke begrenset til, omvisninger, turplanlegging, koordinering av reiseaktiviteter og formidling av informasjon om lokale attraksjoner, historie og kultur, tilbyr også privat transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −610 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −610
Equity
NOK 23,000
Est. value
NOK 33,000

Financial health · 2025

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 NORTHRIDE AS?

MOHAMMAD HAMID NASSIMI
NORTHRIDE AS
NOK 0 rev. · NOK −610 profit

NORTHRIDE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORTHRIDE AS

Who owns NORTHRIDE AS?

MOHAMMAD HAMID NASSIMI is the largest registered owner, with 50.0%.

What is the revenue of NORTHRIDE AS?

NORTHRIDE AS had revenue of NOK 0 in 2025.

Where is NORTHRIDE AS based?

NORTHRIDE AS has its business address in Tromsø.

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.