BIZTRAC BETA
Marine fishing

BLIEN AS

Org. no. 924428724 Limited company (AS) Tana Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −184,000
Equity NOK 962,000
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−184k kr).

BLIEN AS is registered as a limited company in Tana, Finnmark with organisation number 924428724. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Hav og kystfiske samt opplevelse turisme, overnatting, handel med deler og utstyr til motorvogner, motorsykler og snøscooter, graving og planering, utleie av maskiner og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −184,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −184,000
Equity
NOK 962,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns BLIEN AS?

AAGE BLIEN
BLIEN AS
NOK 1.9m rev. · NOK −184,000 profit

BLIEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BLIEN AS own?

BLIEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLIEN AS

Who owns BLIEN AS?

AAGE BLIEN is the largest registered owner, with 51.0%.

What is the revenue of BLIEN AS?

BLIEN AS had revenue of NOK 1.9m in 2025.

Who is the general manager of BLIEN AS?

Aage Blien is registered as general manager of BLIEN AS.

Where is BLIEN AS based?

BLIEN AS has its business address in Tana.

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.