BIZTRAC BETA
Raising of sheep

LARAPINTA AS

Org. no. 927157837 Limited company (AS) Gjerdrum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 589,000
Operating profit NOK −61,000
Equity NOK 100,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

LARAPINTA AS is registered as a limited company in Gjerdrum, Akershus with organisation number 927157837. The business is classified under raising of sheep (NACE 01.451). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Gårdsdrift både med og uten dyrehold. Håndverktjenester, herunder bygg og anlegg, elektrisitet, vann og avløp og fjernvarme. Opplevelsesaktiviteter og events.”. The most recent filed accounts, for the 2024 financial year, show NOK 589,000 in revenue and NOK −61,000 in operating profit.

Key figures · 2024

Revenue
NOK 589,000
Operating profit
NOK −61,000
Equity
NOK 100,000
Est. value
NOK 257,000

Financial health · 2024

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

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

Who owns LARAPINTA AS?

KAI ROBERT KULSRUD
LARAPINTA AS
NOK 589,000 rev. · NOK −61,000 profit

LARAPINTA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LARAPINTA AS

Who owns LARAPINTA AS?

KAI ROBERT KULSRUD is the largest registered owner, with 50.0%.

What is the revenue of LARAPINTA AS?

LARAPINTA AS had revenue of NOK 589,000 in 2024.

Who is the general manager of LARAPINTA AS?

Kai Robert Kulsrud is registered as general manager of LARAPINTA AS.

Where is LARAPINTA AS based?

LARAPINTA AS has its business address in Gjerdrum.

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.