BIZTRAC BETA
Beverage serving activities

FRUKTBAR AS

Org. no. 989583328 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 14,000
Equity NOK 96,000
Incorporated 2006
Employees 14
Share capital NOK 553,000

FRUKTBAR AS is registered as a limited company in Bergen, Vestland with organisation number 989583328. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2006 and has 14 registered employees. Registered share capital is NOK 553,000, divided into 9379 shares. The company's stated purpose is: “Eie og utvikle konsept, navn og varemerke. Drive forretning med salg av smoothies, jus og andre kafévarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 14,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 14,000
Equity
NOK 96,000
Est. value
NOK 84,000

Financial health · 2024

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

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

Who owns FRUKTBAR AS?

STINA THORESEN ANGERMAN
FRUKTBAR AS
NOK 3.9m rev. · NOK 14,000 profit

FRUKTBAR AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FRUKTBAR AS own?

FRUKTBAR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRUKTBAR AS

Who owns FRUKTBAR AS?

STINA THORESEN ANGERMAN is the largest registered owner, with 41.0%.

What is the revenue of FRUKTBAR AS?

FRUKTBAR AS had revenue of NOK 3.9m in 2024.

Who is the general manager of FRUKTBAR AS?

Stina Thoresen Angerman is registered as general manager of FRUKTBAR AS.

Where is FRUKTBAR AS based?

FRUKTBAR 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.