biztrac. BETA
COMPANY REGISTER PROFILE
926560581 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

LARSEN FISK OG TRANSPORT AS

Org. no. 926560581 Limited company (AS) Tromsø Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 334,000
Equity NOK 116,000
Incorporated 2021
Share capital NOK 30,000

LARSEN FISK OG TRANSPORT AS is registered as a limited company in Tromsø, Troms with organisation number 926560581. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Fiske og fangst langs norske kysten.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 334,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
▲ +68 %
Operating profit
NOK 334,000
▲ +402 %
Equity
NOK 116,000
▲ +179 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
22.6%
Very good
Return on total assets
Solidity
8.3%
Weak
Equity as a share of total capital

Who owns LARSEN FISK OG TRANSPORT AS?

LARSEN FISK OG TRANSPORT AS
NOK 2.1m rev. · NOK 334,000 profit

LARSEN FISK OG TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LARSEN FISK OG TRANSPORT AS

Who owns LARSEN FISK OG TRANSPORT AS?

Karl Hugo Larsen is the largest registered owner, with 100.0%.

What is the revenue of LARSEN FISK OG TRANSPORT AS?

LARSEN FISK OG TRANSPORT AS had revenue of NOK 2.1m in 2025.

Who is the general manager of LARSEN FISK OG TRANSPORT AS?

Karl Hugo Larsen is registered as general manager of LARSEN FISK OG TRANSPORT AS.

Where is LARSEN FISK OG TRANSPORT AS based?

LARSEN FISK OG TRANSPORT AS has its business address in Brensholmen.

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.