BIZTRAC BETA
Freight transport by road

TROND FRANK OG TOM FRAKT AS

Org. no. 964431566 Limited company (AS) Alta Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 24.1m
Operating profit NOK 1.7m
Equity NOK 3.9m
Incorporated 1992
Employees 13
Share capital NOK 100,000

TROND FRANK OG TOM FRAKT AS is registered as a limited company in Alta, Finnmark with organisation number 964431566. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1992 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.1m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 24.1m
Operating profit
NOK 1.7m
Equity
NOK 3.9m
Est. value
NOK 7.8m

Financial health · 2025

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

Who owns TROND FRANK OG TOM FRAKT AS?

TFT HOLDING AS
TROND FRANK OG TOM FRAKT AS
NOK 24.1m rev. · NOK 1.7m profit

TROND FRANK OG TOM FRAKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROND FRANK OG TOM FRAKT AS

Who owns TROND FRANK OG TOM FRAKT AS?

TFT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TROND FRANK OG TOM FRAKT AS?

TROND FRANK OG TOM FRAKT AS had revenue of NOK 24.1m in 2025.

Who is the general manager of TROND FRANK OG TOM FRAKT AS?

Trond Ove Skoglund is registered as general manager of TROND FRANK OG TOM FRAKT AS.

Where is TROND FRANK OG TOM FRAKT AS based?

TROND FRANK OG TOM FRAKT AS has its business address in Alta.

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.