BIZTRAC BETA
Scheduled passenger transport by road

FFR BUSS AS

Org. no. 992465581 Limited company (AS) Hammerfest Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 3.9m
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FFR BUSS AS is registered as a limited company in Hammerfest, Finnmark with organisation number 992465581. The business is classified under scheduled passenger transport by road (NACE 49.310). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Person- og godsbefordring, og dermed sammenhengende og beslektet virksomhet, på vegne av morselskapet Veolia Transport Nord AS.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 3.9m
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns FFR BUSS AS?

BOREAL SJØ AS
FFR BUSS AS
NOK 0 rev. · NOK −18,000 profit

FFR BUSS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FFR BUSS AS er morselskap for 19 datterselskaper:

Frequently asked questions about FFR BUSS AS

Who owns FFR BUSS AS?

BOREAL SJØ AS is the largest registered owner, with 100.0%.

What is the revenue of FFR BUSS AS?

FFR BUSS AS had revenue of NOK 0 in 2025.

Where is FFR BUSS AS based?

FFR BUSS AS has its business address in Hammerfest.

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.