BIZTRAC BETA
Growing of other non-perennial crops

4.FARM PARTNER AS

Org. no. 934399692 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 20,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

4.FARM PARTNER AS is registered as a limited company in Bergen, Vestland with organisation number 934399692. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å bygge, eie og drive små plantefabrikker i samarbeid med lokale bønder og gartnere for produksjon og salg av ulike plantevekster, samt det som står i naturlig forbindelse med dette, herunder helt eller delvis eierskap i andre selskap med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 20,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns 4.FARM PARTNER AS?

4.FARM AS
4.FARM PARTNER AS
NOK 0 rev. · NOK −5,000 profit

4.FARM PARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 4.FARM PARTNER AS

Who owns 4.FARM PARTNER AS?

4.FARM AS is the largest registered owner, with 100.0%.

What is the revenue of 4.FARM PARTNER AS?

4.FARM PARTNER AS had revenue of NOK 0 in 2025.

Where is 4.FARM PARTNER AS based?

4.FARM PARTNER AS has its business address in Bergen.

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.