BIZTRAC BETA
Logistics service activities

24/7 LOGISTIKK AS

Org. no. 914067553 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 169,000
Equity NOK 398,000
Incorporated 2014
Share capital NOK 50,000

24/7 LOGISTIKK AS is registered as a limited company in Bergen, Vestland with organisation number 914067553. The business is classified under logistics service activities (NACE 52.250). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Konsulenttjenester,megling av gods på bil og båt og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 169,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 169,000
Equity
NOK 398,000
Est. value
NOK 791,000

Financial health · 2024

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

Who owns 24/7 LOGISTIKK AS?

TOR ARNE VINDENES
24/7 LOGISTIKK AS
NOK 6.8m rev. · NOK 169,000 profit

24/7 LOGISTIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 24/7 LOGISTIKK AS

Who owns 24/7 LOGISTIKK AS?

TOR ARNE VINDENES is the largest registered owner, with 100.0%.

What is the revenue of 24/7 LOGISTIKK AS?

24/7 LOGISTIKK AS had revenue of NOK 6.8m in 2024.

Who is the general manager of 24/7 LOGISTIKK AS?

Tor Arne Vindenes is registered as general manager of 24/7 LOGISTIKK AS.

Where is 24/7 LOGISTIKK AS based?

24/7 LOGISTIKK AS has its business address in Fyllingsdalen.

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.