BIZTRAC BETA
Restaurant activities

SØSTRENES KAMMERS AS

Org. no. 997953592 Limited company (AS) Tydal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 854,000
Operating profit NOK 3,000
Equity NOK −62,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

SØSTRENES KAMMERS AS is registered as a limited company in Tydal, Trøndelag with organisation number 997953592. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kafe og gave-og interiørbutikk, og annen nærliggende forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 854,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 854,000
Operating profit
NOK 3,000
Equity
NOK −62,000
Est. value
NOK 15,000

Financial health · 2024

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-46.9%
Weak
Equity as a share of total capital

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

Who owns SØSTRENES KAMMERS AS?

OLE BJARNE ØSTBY
SØSTRENES KAMMERS AS
NOK 854,000 rev. · NOK 3,000 profit

SØSTRENES KAMMERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØSTRENES KAMMERS AS

Who owns SØSTRENES KAMMERS AS?

OLE BJARNE ØSTBY is the largest registered owner, with 100.0%.

What is the revenue of SØSTRENES KAMMERS AS?

SØSTRENES KAMMERS AS had revenue of NOK 854,000 in 2024.

Who is the general manager of SØSTRENES KAMMERS AS?

Anne Berit Gipling is registered as general manager of SØSTRENES KAMMERS AS.

Where is SØSTRENES KAMMERS AS based?

SØSTRENES KAMMERS AS has its business address in Tydal.

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.