BIZTRAC BETA
Development of building projects

HINNA STASJON UTVIKLING AS

Org. no. 919524146 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −1.7m
Equity NOK −2.5m
Incorporated 2017
Share capital NOK 1.0m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).
  • Nylig endring 2026-06-25 Aksjekapital registrert 2026-06-25.

HINNA STASJON UTVIKLING AS is registered as a limited company in Stavanger, Rogaland with organisation number 919524146. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 500 shares. The company's stated purpose is: “Erverve, utvikle, oppføre og selge fast eiendom og alt som står i naturlig forbindelse med dette. Samt investere i selskaper med samme formål.”.

Key figures · 2024

Operating profit
NOK −1.7m
Equity
NOK −2.5m

Financial health · 2024

Liquidity
129.66
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19.2%
Weak
Equity as a share of total capital

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

Who owns HINNA STASJON UTVIKLING AS?

BANE NOR EIENDOM AS
HINNA STASJON UTVIKLING AS
· NOK −1.7m profit

HINNA STASJON UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HINNA STASJON UTVIKLING AS

Who owns HINNA STASJON UTVIKLING AS?

BANE NOR EIENDOM AS is the largest registered owner, with 50.0%.

Who is the general manager of HINNA STASJON UTVIKLING AS?

Brit Sølvi Sandstøl is registered as general manager of HINNA STASJON UTVIKLING AS.

Where is HINNA STASJON UTVIKLING AS based?

HINNA STASJON UTVIKLING AS has its business address in Stavanger.

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.