BIZTRAC BETA
Growing of pome fruits and stone fruits

SMAKSRIKET AS

Org. no. 918787291 Limited company (AS) Lier Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 37.9m
Operating profit NOK 826,000
Equity NOK 7.4m
Incorporated 2017
Employees 17
Share capital NOK 1.0m

SMAKSRIKET AS is registered as a limited company in Lier, Buskerud with organisation number 918787291. The business is classified under growing of pome fruits and stone fruits (NACE 01.240). The company was incorporated in 2017 and has 17 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Produksjon og omsetning av økologisk frukt og grønnsaker, samt virksomhet som naturlig hører til under dette. Pakking og salg av egenproduserte varer, samt leiepakking for andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 37.9m in revenue and NOK 826,000 in operating profit.

Key figures · 2025

Revenue
NOK 37.9m
Operating profit
NOK 826,000
Equity
NOK 7.4m
Est. value
NOK 7.2m

Financial health · 2025

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

Who owns SMAKSRIKET AS?

HØRTEBONDEN AS
SMAKSRIKET AS
NOK 37.9m rev. · NOK 826,000 profit

SMAKSRIKET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SMAKSRIKET AS er morselskap for 2 datterselskaper:

Frequently asked questions about SMAKSRIKET AS

Who owns SMAKSRIKET AS?

HØRTEBONDEN AS is the largest registered owner, with 100.0%.

What is the revenue of SMAKSRIKET AS?

SMAKSRIKET AS had revenue of NOK 37.9m in 2025.

Who is the general manager of SMAKSRIKET AS?

Anders Hørthe is registered as general manager of SMAKSRIKET AS.

Where is SMAKSRIKET AS based?

SMAKSRIKET AS has its business address in Sylling.

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.