BIZTRAC BETA
Non-scheduled passenger transport by road

S RØNSÅSBJØRG AS

Org. no. 913851889 Limited company (AS) Stjørdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −35,000
Equity NOK 3.4m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−35k kr).

S RØNSÅSBJØRG AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 913851889. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av turbiltransport, busstransport, persontransport og opplæring innen busskjøring samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −35,000
Equity
NOK 3.4m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns S RØNSÅSBJØRG AS?

BJØRN OVE RØNSÅSBJØRG
S RØNSÅSBJØRG AS
NOK 0 rev. · NOK −35,000 profit

S RØNSÅSBJØRG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does S RØNSÅSBJØRG AS own?

S RØNSÅSBJØRG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about S RØNSÅSBJØRG AS

Who owns S RØNSÅSBJØRG AS?

BJØRN OVE RØNSÅSBJØRG is the largest registered owner, with 90.0%.

What is the revenue of S RØNSÅSBJØRG AS?

S RØNSÅSBJØRG AS had revenue of NOK 0 in 2024.

Where is S RØNSÅSBJØRG AS based?

S RØNSÅSBJØRG AS has its business address in Stjørdal.

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.