BIZTRAC BETA
Freight transport by road

BLINKEN TRANSPORT AS

Org. no. 931018825 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 863,000
Operating profit NOK 58,000
Equity NOK 171,000
Incorporated 2023
Share capital NOK 30,000

BLINKEN TRANSPORT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 931018825. The business is classified under freight transport by road (NACE 49.410). 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 veitransport, varesalg, utleie av maskiner og utstyr - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 863,000 in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 863,000
Operating profit
NOK 58,000
Equity
NOK 171,000
Est. value
NOK 287,000

Financial health · 2025

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

Who owns BLINKEN TRANSPORT AS?

ERIK ANDRÉ BROE
BLINKEN TRANSPORT AS
NOK 863,000 rev. · NOK 58,000 profit

BLINKEN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLINKEN TRANSPORT AS

Who owns BLINKEN TRANSPORT AS?

ERIK ANDRÉ BROE is the largest registered owner, with 50.0%.

What is the revenue of BLINKEN TRANSPORT AS?

BLINKEN TRANSPORT AS had revenue of NOK 863,000 in 2025.

Who is the general manager of BLINKEN TRANSPORT AS?

Hilde Broe is registered as general manager of BLINKEN TRANSPORT AS.

Where is BLINKEN TRANSPORT AS based?

BLINKEN TRANSPORT 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.