BIZTRAC BETA
Rental and operating of own or leased real estate

STASJONSBYGGET AS

Org. no. 921550065 Limited company (AS) Øygarden Incorporated 1978 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK −61,000
Equity NOK 11.9m
Incorporated 1978
Share capital NOK 2.0m

Signals

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

STASJONSBYGGET AS is registered as a limited company in Øygarden, Vestland with organisation number 921550065. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1978. Registered share capital is NOK 2.0m, divided into 1966 shares. The company's stated purpose is: “Eiendomsutvikling, utbygging, utleie av fast eiendom samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK −61,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK −61,000
Equity
NOK 11.9m
Est. value
NOK 9.6m

Financial health · 2025

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

Who owns STASJONSBYGGET AS?

JALO HOLDING AS
STASJONSBYGGET AS
NOK 2.0m rev. · NOK −61,000 profit

STASJONSBYGGET AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about STASJONSBYGGET AS

Who owns STASJONSBYGGET AS?

JALO HOLDING AS is the largest registered owner, with 35.0%.

What is the revenue of STASJONSBYGGET AS?

STASJONSBYGGET AS had revenue of NOK 2.0m in 2025.

Who is the general manager of STASJONSBYGGET AS?

Johnny Anders Straume is registered as general manager of STASJONSBYGGET AS.

Where is STASJONSBYGGET AS based?

STASJONSBYGGET AS has its business address in Straume.

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.