BIZTRAC BETA
Event catering activities

STØRDAL GÅRD AS

Org. no. 925856185 Limited company (AS) Tvedestrand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 141,000
Equity NOK 414,000
Incorporated 2020
Employees 10
Share capital NOK 30,000

STØRDAL GÅRD AS is registered as a limited company in Tvedestrand, Agder with organisation number 925856185. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2020 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Gårdsutsalg med egenproduserte og innkjøpte varer. Drift av selskapslokaler med tilhørende servering og ellers hva som naturlig hører inn under dette. Selskapet kan ha eierandeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 141,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 141,000
Equity
NOK 414,000
Est. value
NOK 752,000

Financial health · 2025

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

Who owns STØRDAL GÅRD AS?

BRITT ELISABETH FOSSDAL
STØRDAL GÅRD AS
NOK 3.2m rev. · NOK 141,000 profit

STØRDAL GÅRD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STØRDAL GÅRD AS

Who owns STØRDAL GÅRD AS?

BRITT ELISABETH FOSSDAL is the largest registered owner, with 50.0%.

What is the revenue of STØRDAL GÅRD AS?

STØRDAL GÅRD AS had revenue of NOK 3.2m in 2025.

Who is the general manager of STØRDAL GÅRD AS?

Britt Elisabeth Fossdal is registered as general manager of STØRDAL GÅRD AS.

Where is STØRDAL GÅRD AS based?

STØRDAL GÅRD AS has its business address in Tvedestrand.

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.