BIZTRAC BETA
Freight transport by road

S E BETTEN TRANSPORT AS

Org. no. 913169700 Limited company (AS) Tana Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 938,000
Operating profit NOK −35,000
Equity NOK 322,000
Incorporated 2014
Share capital NOK 100,000

Signals

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

S E BETTEN TRANSPORT AS is registered as a limited company in Tana, Finnmark with organisation number 913169700. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport og annet som naturlig faller sammen med det.”. The most recent filed accounts, for the 2025 financial year, show NOK 938,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 938,000
Operating profit
NOK −35,000
Equity
NOK 322,000
Est. value
NOK 600,000

Financial health · 2024

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

Who owns S E BETTEN TRANSPORT AS?

SVEIN ERIK BETTEN
S E BETTEN TRANSPORT AS
NOK 938,000 rev. · NOK −35,000 profit

S E BETTEN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about S E BETTEN TRANSPORT AS

Who owns S E BETTEN TRANSPORT AS?

SVEIN ERIK BETTEN is the largest registered owner, with 75.0%.

What is the revenue of S E BETTEN TRANSPORT AS?

S E BETTEN TRANSPORT AS had revenue of NOK 938,000 in 2025.

Who is the general manager of S E BETTEN TRANSPORT AS?

Svein Erik Betten is registered as general manager of S E BETTEN TRANSPORT AS.

Where is S E BETTEN TRANSPORT AS based?

S E BETTEN TRANSPORT AS has its business address in Tana.

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.