biztrac. BETA
COMPANY REGISTER PROFILE
980836150 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Removal services

ANTONSEN T-LINE AS

Org. no. 980836150 Limited company (AS) Øksnes Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 241,000
Equity NOK 641,000
Incorporated 1999
Employees 11
Share capital NOK 550,000

ANTONSEN T-LINE AS is registered as a limited company in Øksnes, Nordland with organisation number 980836150. The business is classified under removal services (NACE 49.420). The company was incorporated in 1999 and has 11 registered employees. Registered share capital is NOK 550,000, divided into 5500 shares. The company's stated purpose is: “Lastebilvirksomhet, flyttetransport og hertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 241,000 in operating profit.

Former names: T LINE AS

Key figures · 2025

Revenue
NOK 6.1m
▼ −16 %
Operating profit
NOK 241,000
▲ +1144 %
Equity
NOK 641,000
▲ +40 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
12.7%
Good
Return on total assets
Solidity
41.6%
Very good
Equity as a share of total capital

Who owns ANTONSEN T-LINE AS?

ANTONSEN T-LINE AS
NOK 6.1m rev. · NOK 241,000 profit

ANTONSEN T-LINE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANTONSEN T-LINE AS

Who owns ANTONSEN T-LINE AS?

Per-Einar Antonsen is the largest registered owner, with 50.0%.

What is the revenue of ANTONSEN T-LINE AS?

ANTONSEN T-LINE AS had revenue of NOK 6.1m in 2025.

Who is the general manager of ANTONSEN T-LINE AS?

Per-Einar Antonsen is registered as general manager of ANTONSEN T-LINE AS.

Where is ANTONSEN T-LINE AS based?

ANTONSEN T-LINE AS has its business address in Sortland.

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.