BIZTRAC BETA
Scheduled passenger transport by road

STORDAL BILLAG AS

Org. no. 931683659 Limited company (AS) Fjord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK −23,000
Equity NOK 546,000
Incorporated 2023
Employees 6
Share capital NOK 30,000

Signals

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

STORDAL BILLAG AS is registered as a limited company in Fjord, Møre og Romsdal with organisation number 931683659. The business is classified under scheduled passenger transport by road (NACE 49.310). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Persontransport, og annen transport, herunder også å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK −23,000
Equity
NOK 546,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.5%
Satisfactory
Equity as a share of total capital

Who owns STORDAL BILLAG AS?

FRANK EINAR STØLE OLSEN
STORDAL BILLAG AS
NOK 4.4m rev. · NOK −23,000 profit

STORDAL BILLAG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORDAL BILLAG AS

Who owns STORDAL BILLAG AS?

FRANK EINAR STØLE OLSEN is the largest registered owner, with 33.3%.

What is the revenue of STORDAL BILLAG AS?

STORDAL BILLAG AS had revenue of NOK 4.4m in 2025.

Who is the general manager of STORDAL BILLAG AS?

Bjørn Ove Olsen is registered as general manager of STORDAL BILLAG AS.

Where is STORDAL BILLAG AS based?

STORDAL BILLAG AS has its business address in Stordal.

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.