BIZTRAC BETA
Office administrative and support activities

FISHBILLING AS

Org. no. 882778452 Limited company (AS) Nærøysund Incorporated 2000 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 11,000
Incorporated 2000
Share capital NOK 243,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

FISHBILLING AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 882778452. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2000. Registered share capital is NOK 243,000, divided into 175 shares. The company's stated purpose is: “Elektronisk fakturering av fisk og sjømat, utvikling av finansieringsinstrumenter i sammenheng med netthandel av fisk, kundestøttesystemer og annen virksomhet i forbindelse med dette. I tillegg kan selskapet investere i aksjer i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −7,000
Equity
NOK 11,000
Est. value
NOK 16,000

Financial health · 2024

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

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

Who owns FISHBILLING AS?

LARS PEDER BREKK
FISHBILLING AS
· NOK −7,000 profit

FISHBILLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FISHBILLING AS own?

FISHBILLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FISHBILLING AS

Who owns FISHBILLING AS?

LARS PEDER BREKK is the largest registered owner, with 100.0%.

Who is the general manager of FISHBILLING AS?

Sofie Margaret Leirvik is registered as general manager of FISHBILLING AS.

Where is FISHBILLING AS based?

FISHBILLING AS has its business address in Rørvik.

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.