BIZTRAC BETA
Combined facilities support activities

HINDØY SOLUTIONS AS

Org. no. 934922247 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 146,000
Operating profit NOK 144,000
Equity NOK 139,000
Incorporated 2025
Share capital NOK 30,000

HINDØY SOLUTIONS AS is registered as a limited company in Stavanger, Rogaland with organisation number 934922247. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen vaktmesterarbeid og annet som naturlig sammenfaller med dette, samt deltagelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 146,000 in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 146,000
Operating profit
NOK 144,000
Equity
NOK 139,000
Est. value
NOK 539,000

Financial health · 2025

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

Who owns HINDØY SOLUTIONS AS?

JOHN OLAV HINDØY
HINDØY SOLUTIONS AS
NOK 146,000 rev. · NOK 144,000 profit

HINDØY SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HINDØY SOLUTIONS AS

Who owns HINDØY SOLUTIONS AS?

JOHN OLAV HINDØY is the largest registered owner, with 100.0%.

What is the revenue of HINDØY SOLUTIONS AS?

HINDØY SOLUTIONS AS had revenue of NOK 146,000 in 2025.

Who is the general manager of HINDØY SOLUTIONS AS?

John Olav Hindøy is registered as general manager of HINDØY SOLUTIONS AS.

Where is HINDØY SOLUTIONS AS based?

HINDØY SOLUTIONS AS has its business address in Hundvåg.

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.