BIZTRAC BETA
Technical testing and analysis

RESIPIENTANALYSE AS

Org. no. 998058376 Limited company (AS) Bjørnafjorden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 22,000
Equity NOK 12,000
Incorporated 2012
Share capital NOK 300,000

RESIPIENTANALYSE AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 998058376. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2012. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Yte tjenester innenfor miljøkartlegging og annen relatert virksomhet, herunder salg av konsulenttjenester, og deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 22,000
Equity
NOK 12,000
Est. value
NOK 80,000

Financial health · 2025

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.2%
Weak
Equity as a share of total capital

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

Who owns RESIPIENTANALYSE AS?

FRODE HAVELAND
RESIPIENTANALYSE AS
NOK 1.2m rev. · NOK 22,000 profit

RESIPIENTANALYSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESIPIENTANALYSE AS

Who owns RESIPIENTANALYSE AS?

FRODE HAVELAND is the largest registered owner, with 100.0%.

What is the revenue of RESIPIENTANALYSE AS?

RESIPIENTANALYSE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of RESIPIENTANALYSE AS?

Frode Haveland is registered as general manager of RESIPIENTANALYSE AS.

Where is RESIPIENTANALYSE AS based?

RESIPIENTANALYSE AS has its business address in Søfteland.

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.