BIZTRAC BETA
Other postal and courier activities

LIN TRANSPORT AS

Org. no. 921221223 Limited company (AS) Frogn Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 1.0m
Equity NOK −1.1m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).

LIN TRANSPORT AS is registered as a limited company in Frogn, Akershus with organisation number 921221223. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Budbiltransport, utleie av biler og dessuten være deltaker i annen forretningsvirksomhet, andre selskaper og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 1.0m
Equity
NOK −1.1m
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-377.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LIN TRANSPORT AS?

MEIQING LIN
LIN TRANSPORT AS
NOK 3.0m rev. · NOK 1.0m profit

LIN TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIN TRANSPORT AS

Who owns LIN TRANSPORT AS?

MEIQING LIN is the largest registered owner, with 50.0%.

What is the revenue of LIN TRANSPORT AS?

LIN TRANSPORT AS had revenue of NOK 3.0m in 2025.

Who is the general manager of LIN TRANSPORT AS?

Meiqing Lin is registered as general manager of LIN TRANSPORT AS.

Where is LIN TRANSPORT AS based?

LIN TRANSPORT AS has its business address in Drøbak.

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.