BIZTRAC BETA
Computer programming activities

FARMABLE AS

Org. no. 821604702 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 645,000
Operating profit NOK −16.7m
Equity NOK 42.1m
Incorporated 2018
Share capital NOK 122,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16,7 mill kr).
  • Nylig endring 2026-04-20 Aksjekapital registrert 2026-04-20.

FARMABLE AS is registered as a limited company in Drammen, Buskerud with organisation number 821604702. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 122,000, divided into 4077262 shares. The company's stated purpose is: “Utvikling og salg av programvare, rådgivning og tjenester i forbindelse med dette i landbruket og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 645,000 in revenue and NOK −16.7m in operating profit.

Key figures · 2024

Revenue
NOK 645,000
Operating profit
NOK −16.7m
Equity
NOK 42.1m
Est. value
NOK 19.1m

Financial health · 2024

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

Who owns FARMABLE AS?

NORSELAB F I FAM AS
FARMABLE AS
NOK 645,000 rev. · NOK −16.7m profit

FARMABLE AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about FARMABLE AS

Who owns FARMABLE AS?

NORSELAB F I FAM AS is the largest registered owner, with 41.8%.

What is the revenue of FARMABLE AS?

FARMABLE AS had revenue of NOK 645,000 in 2024.

Who is the general manager of FARMABLE AS?

Lars Petter Blikom is registered as general manager of FARMABLE AS.

Where is FARMABLE AS based?

FARMABLE AS has its business address in Svelvik.

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.