BIZTRAC BETA
COMPANY REGISTER PROFILE
912323048 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Marine fishing

BJØRSVIK HAVFISKE AS

Org. no. 912323048 Limited company (AS) Flatanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 97,000
Operating profit NOK 24,000
Equity NOK 136,000
Incorporated 2013
Share capital NOK 185,000

Signals

1 flags
  • Nylig endring 2026-08-25 Avregistrert registrert 2026-08-25.

BJØRSVIK HAVFISKE AS is registered as a limited company in Flatanger, Trøndelag with organisation number 912323048. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2013. Registered share capital is NOK 185,000, divided into 185 shares. The company's stated purpose is: “Drive fiske og fangst, turistkjøring og alt som for øvrig står i naturlig sammenheng med dette, samt delta i annen virksomhet(er) som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 97,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 97,000
Operating profit
NOK 24,000
Equity
NOK 136,000

Financial health · 2025

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

Who owns BJØRSVIK HAVFISKE AS?

BJØRSVIK HAVFISKE AS
NOK 97,000 rev. · NOK 24,000 profit

BJØRSVIK HAVFISKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRSVIK HAVFISKE AS

Who owns BJØRSVIK HAVFISKE AS?

PATRICK BJØRSVIK DAHLE is the largest registered owner, with 81.1%.

What is the revenue of BJØRSVIK HAVFISKE AS?

BJØRSVIK HAVFISKE AS had revenue of NOK 97,000 in 2025.

Where is BJØRSVIK HAVFISKE AS based?

BJØRSVIK HAVFISKE AS has its business address in Flatanger.

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

Report a problem

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