BIZTRAC BETA
Wholesale of other intermediate products

PEREGRINE NORGE AS

Org. no. 924548843 Limited company (AS) Gjesdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 90,000
Incorporated 2020
Share capital NOK 48,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

PEREGRINE NORGE AS is registered as a limited company in Gjesdal, Rogaland with organisation number 924548843. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 2020. Registered share capital is NOK 48,000, divided into 48 shares. The company's stated purpose is: “Å levere tjenester/produkter innen import, salg og produksjon av ammunisjon og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 90,000
Est. value
NOK 113,000

Financial health · 2025

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

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

Who owns PEREGRINE NORGE AS?

BUAS OUTDOORS AS
PEREGRINE NORGE AS
NOK 0 rev. · NOK −13,000 profit

PEREGRINE NORGE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PEREGRINE NORGE AS

Who owns PEREGRINE NORGE AS?

BUAS OUTDOORS AS is the largest registered owner, with 81.2%.

What is the revenue of PEREGRINE NORGE AS?

PEREGRINE NORGE AS had revenue of NOK 0 in 2025.

Where is PEREGRINE NORGE AS based?

PEREGRINE NORGE AS has its business address in Ålgård.

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.