BIZTRAC BETA
Logistics service activities

BROKER LOGISTIKK AS

Org. no. 831143932 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 25.0m
Operating profit NOK 33,000
Equity NOK 479,000
Incorporated 2023
Share capital NOK 30,000

BROKER LOGISTIKK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 831143932. The business is classified under logistics service activities (NACE 52.250). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen Spedisjon og logistikk innen godstransport på vei. - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.0m in revenue and NOK 33,000 in operating profit.

Key figures · 2024

Revenue
NOK 25.0m
Operating profit
NOK 33,000
Equity
NOK 479,000
Est. value
NOK 341,000

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.1%
Weak
Equity as a share of total capital

Who owns BROKER LOGISTIKK AS?

1978 INVEST AS
BROKER LOGISTIKK AS
NOK 25.0m rev. · NOK 33,000 profit

BROKER LOGISTIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROKER LOGISTIKK AS

Who owns BROKER LOGISTIKK AS?

1978 INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BROKER LOGISTIKK AS?

BROKER LOGISTIKK AS had revenue of NOK 25.0m in 2024.

Who is the general manager of BROKER LOGISTIKK AS?

Marius Lervold is registered as general manager of BROKER LOGISTIKK AS.

Where is BROKER LOGISTIKK AS based?

BROKER LOGISTIKK AS has its business address in Skjetten.

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.