biztrac. BETA
COMPANY REGISTER PROFILE
913885198 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Leasing of intellectual property and similar products, except copyrighted works

FISHLEC AS

Org. no. 913885198 Limited company (AS) Bergen Incorporated 2014 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −120,000
Incorporated 2014
Share capital NOK 33,000

Signals

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

FISHLEC AS is registered as a limited company in Bergen, Vestland with organisation number 913885198. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2014. Registered share capital is NOK 33,000, divided into 32571 shares. The company's stated purpose is: “Omsetning og annen utnyttelse av immaterialle rettigheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: FARMLEC AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
▲ +100 %
Equity
NOK −120,000
▼ −0 %

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
-716.7%
Weak
Equity as a share of total capital

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

Who owns FISHLEC AS?

FISHLEC AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about FISHLEC AS

Who owns FISHLEC AS?

Mirushe Miftari is the largest registered owner, with 45.4%.

What is the revenue of FISHLEC AS?

FISHLEC AS had revenue of NOK 0 in 2025.

Who is the general manager of FISHLEC AS?

Mirushe Miftari is registered as general manager of FISHLEC AS.

Where is FISHLEC AS based?

FISHLEC AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.