BIZTRAC BETA
Other support activities for transportation

LOGI TRANS TERMINAL AS

Org. no. 889636432 Limited company (AS) Sola Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 12.0m
Operating profit NOK 8.5m
Equity NOK 6.2m
Incorporated 2006
Share capital NOK 2.2m

LOGI TRANS TERMINAL AS is registered as a limited company in Sola, Rogaland with organisation number 889636432. The business is classified under other support activities for transportation (NACE 52.260). The company was incorporated in 2006. Registered share capital is NOK 2.2m, divided into 2219196 shares. The company's stated purpose is: “Eie og forvalte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.0m in revenue and NOK 8.5m in operating profit.

Key figures · 2024

Revenue
NOK 12.0m
Operating profit
NOK 8.5m
Equity
NOK 6.2m
Est. value
NOK 22.3m

Financial health · 2025

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

Who owns LOGI TRANS TERMINAL AS?

LOGI TRANS GROUP AS
LOGI TRANS TERMINAL AS
NOK 12.0m rev. · NOK 8.5m profit

LOGI TRANS TERMINAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOGI TRANS TERMINAL AS own?

LOGI TRANS TERMINAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOGI TRANS TERMINAL AS

Who owns LOGI TRANS TERMINAL AS?

LOGI TRANS GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of LOGI TRANS TERMINAL AS?

LOGI TRANS TERMINAL AS had revenue of NOK 12.0m in 2024.

Who is the general manager of LOGI TRANS TERMINAL AS?

Else Cathrine Kjernes Ogne is registered as general manager of LOGI TRANS TERMINAL AS.

Where is LOGI TRANS TERMINAL AS based?

LOGI TRANS TERMINAL AS has its business address in Tananger.

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.