BIZTRAC BETA
Camping grounds and recreational vehicle parks

SMØRDAL HYTTEUTLEIGE OG CAMPING AS

Org. no. 913109880 Limited company (AS) Stad Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK 33,000
Equity NOK −748,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−748k kr).

SMØRDAL HYTTEUTLEIGE OG CAMPING AS is registered as a limited company in Stad, Vestland with organisation number 913109880. The business is classified under camping grounds and recreational vehicle parks (NACE 55.300). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive campingplass og kjøp og sal av varer og tenester som høyrer inn under dette. Selskapet kan og delta i andre selskap.”.

Key figures · 2024

Operating profit
NOK 33,000
Equity
NOK −748,000
Est. value
NOK 200,000

Financial health · 2024

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

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

Who owns SMØRDAL HYTTEUTLEIGE OG CAMPING AS?

FORSELL EIENDOM AS
SMØRDAL HYTTEUTLEIGE OG CAMPING AS
· NOK 33,000 profit

SMØRDAL HYTTEUTLEIGE OG CAMPING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMØRDAL HYTTEUTLEIGE OG CAMPING AS

Who owns SMØRDAL HYTTEUTLEIGE OG CAMPING AS?

FORSELL EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of SMØRDAL HYTTEUTLEIGE OG CAMPING AS?

Bjørg Dagmar Forsell is registered as general manager of SMØRDAL HYTTEUTLEIGE OG CAMPING AS.

Where is SMØRDAL HYTTEUTLEIGE OG CAMPING AS based?

SMØRDAL HYTTEUTLEIGE OG CAMPING AS has its business address in Nordfjordeid.

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.