BIZTRAC BETA
Combined facilities support activities

SINES TRANSPORT AS

Org. no. 831547782 Limited company (AS) Froland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 13,000
Operating profit NOK −33,000
Equity NOK 33,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SINES TRANSPORT AS is registered as a limited company in Froland, Agder with organisation number 831547782. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vaktmestertjenester og utleie av maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 13,000
Operating profit
NOK −33,000
Equity
NOK 33,000
Est. value
NOK 25,000

Financial health · 2025

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

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

Who owns SINES TRANSPORT AS?

BJØRN ARILD SINES
SINES TRANSPORT AS
NOK 13,000 rev. · NOK −33,000 profit

SINES TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SINES TRANSPORT AS

Who owns SINES TRANSPORT AS?

BJØRN ARILD SINES is the largest registered owner, with 100.0%.

What is the revenue of SINES TRANSPORT AS?

SINES TRANSPORT AS had revenue of NOK 13,000 in 2025.

Who is the general manager of SINES TRANSPORT AS?

Bjørn Arild Sines is registered as general manager of SINES TRANSPORT AS.

Where is SINES TRANSPORT AS based?

SINES TRANSPORT AS has its business address in Froland.

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.