BIZTRAC BETA
Other services incidental to land transport n.e.c.

FOLGEBIL SØR AS

Org. no. 926195654 Limited company (AS) Lindesnes Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 321,000
Operating profit NOK 953
Equity NOK −201,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

FOLGEBIL SØR AS is registered as a limited company in Lindesnes, Agder with organisation number 926195654. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenester tilknyttet til spesialtransport som ledsager et annet kjøretøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 321,000 in revenue and NOK 953 in operating profit.

Key figures · 2025

Revenue
NOK 321,000
Operating profit
NOK 953
Equity
NOK −201,000
Est. value
NOK 6,000

Financial health · 2025

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

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

Who owns FOLGEBIL SØR AS?

TORBJØRN OLSEN
FOLGEBIL SØR AS
NOK 321,000 rev. · NOK 953 profit

FOLGEBIL SØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLGEBIL SØR AS

Who owns FOLGEBIL SØR AS?

TORBJØRN OLSEN is the largest registered owner, with 100.0%.

What is the revenue of FOLGEBIL SØR AS?

FOLGEBIL SØR AS had revenue of NOK 321,000 in 2025.

Who is the general manager of FOLGEBIL SØR AS?

Torbjørn Olsen is registered as general manager of FOLGEBIL SØR AS.

Where is FOLGEBIL SØR AS based?

FOLGEBIL SØR AS has its business address in Mandal.

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.