biztrac. BETA
COMPANY REGISTER PROFILE
930998249 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

FAST BOKS AS

Org. no. 930998249 Limited company (AS) Råde Incorporated 2023 Active
Revenue 2025 NOK 2.1m
Operating profit NOK −392,000
Equity NOK −575,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−575k kr).

FAST BOKS AS is registered as a limited company in Råde, Østfold with organisation number 930998249. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Godstransport på vei.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −392,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
▲ +38 %
Operating profit
NOK −392,000
▼ −591 %
Equity
NOK −575,000
▼ −282 %

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
-95.1%
Not satisfactory
Return on total assets
Solidity
-98.6%
Weak
Equity as a share of total capital

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

Who owns FAST BOKS AS?

FAST BOKS AS
NOK 2.1m rev. · NOK −392,000 profit

FAST BOKS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FAST BOKS AS

Who owns FAST BOKS AS?

Liviu-Daniel Florescu is the largest registered owner, with 100.0%.

What is the revenue of FAST BOKS AS?

FAST BOKS AS had revenue of NOK 2.1m in 2025.

Who is the general manager of FAST BOKS AS?

Liviu-Daniel Florescu is registered as general manager of FAST BOKS AS.

Where is FAST BOKS AS based?

FAST BOKS AS has its business address in Råde.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.