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

BULLGÅRDEN KYSTFISKE AS

Org. no. 928906728 Limited company (AS) Hasvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 609,000
Equity NOK 548,000
Incorporated 2022
Share capital NOK 380,000

BULLGÅRDEN KYSTFISKE AS is registered as a limited company in Hasvik, Finnmark with organisation number 928906728. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2022. Registered share capital is NOK 380,000, divided into 38000 shares. The company's stated purpose is: “Fiske og fangst, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 609,000 in operating profit.

Former names: AFAS 270222-7 AS

Key figures · 2025

Revenue
NOK 1.5m
▲ +229 %
Operating profit
NOK 609,000
▲ +14718 %
Equity
NOK 548,000
▲ +267 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
4.75
Very good
Current assets ÷ current liabilities
Profitability
55.5%
Very good
Return on total assets
Solidity
38.2%
Good
Equity as a share of total capital

Who owns BULLGÅRDEN KYSTFISKE AS?

BULLGÅRDEN KYSTFISKE AS
NOK 1.5m rev. · NOK 609,000 profit

BULLGÅRDEN KYSTFISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BULLGÅRDEN KYSTFISKE AS

Who owns BULLGÅRDEN KYSTFISKE AS?

F.J HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BULLGÅRDEN KYSTFISKE AS?

BULLGÅRDEN KYSTFISKE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of BULLGÅRDEN KYSTFISKE AS?

Freddi Johansen is registered as general manager of BULLGÅRDEN KYSTFISKE AS.

Where is BULLGÅRDEN KYSTFISKE AS based?

BULLGÅRDEN KYSTFISKE AS has its business address in Hasvik.

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.