BIZTRAC BETA
Contract catering service activities and other food service activities

HUNDSUND SKOLERESTAURANT AS

Org. no. 993135828 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 219,000
Equity NOK 1.3m
Incorporated 2008
Share capital NOK 580,000

HUNDSUND SKOLERESTAURANT AS is registered as a limited company in Bærum, Akershus with organisation number 993135828. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 2008. Registered share capital is NOK 580,000, divided into 580 shares. The company's stated purpose is: “Skolerestaurant og catering virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 219,000
Equity
NOK 1.3m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns HUNDSUND SKOLERESTAURANT AS?

SNARØYA FAMILIELAG
HUNDSUND SKOLERESTAURANT AS
NOK 5.0m rev. · NOK 219,000 profit

HUNDSUND SKOLERESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUNDSUND SKOLERESTAURANT AS

Who owns HUNDSUND SKOLERESTAURANT AS?

SNARØYA FAMILIELAG is the largest registered owner, with 100.0%.

What is the revenue of HUNDSUND SKOLERESTAURANT AS?

HUNDSUND SKOLERESTAURANT AS had revenue of NOK 5.0m in 2025.

Who is the general manager of HUNDSUND SKOLERESTAURANT AS?

Roar Padderud is registered as general manager of HUNDSUND SKOLERESTAURANT AS.

Where is HUNDSUND SKOLERESTAURANT AS based?

HUNDSUND SKOLERESTAURANT AS has its business address in Fornebu.

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.