BIZTRAC BETA
Wholesale of fruit and vegetables

KRISPY AS

Org. no. 926490168 Limited company (AS) Tønsberg Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −117,000
Equity NOK −252,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−252k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−117k kr).

KRISPY AS is registered as a limited company in Tønsberg, Vestfold with organisation number 926490168. The business is classified under wholesale of fruit and vegetables (NACE 46.310). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Salg og produksjon av frysetørket overskuddsfrukt, grønt og bær fra lokale virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −117,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −117,000
Equity
NOK −252,000

Financial health · 2024

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

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

Who owns KRISPY AS?

BENJAMIN ABRAHAMSEN BENDU
KRISPY AS
NOK 1.0m rev. · NOK −117,000 profit

KRISPY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRISPY AS

Who owns KRISPY AS?

BENJAMIN ABRAHAMSEN BENDU is the largest registered owner, with 50.0%.

What is the revenue of KRISPY AS?

KRISPY AS had revenue of NOK 1.0m in 2024.

Who is the general manager of KRISPY AS?

Silje Eikeland Hansen is registered as general manager of KRISPY AS.

Where is KRISPY AS based?

KRISPY AS has its business address in Tolvsrød.

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.