BIZTRAC BETA
Retail sale of textiles

RYGGE GARN AS

Org. no. 930569879 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK −55,000
Equity NOK −817,000
Incorporated 2022
Employees 9
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−817k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−55k kr).

RYGGE GARN AS is registered as a limited company in Moss, Østfold with organisation number 930569879. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Detaljhandel med garn og strikkeprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK −55,000
Equity
NOK −817,000

Financial health · 2025

Liquidity
2.10
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-51.3%
Weak
Equity as a share of total capital

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

Who owns RYGGE GARN AS?

Camilla Schilling Tønnesen
RYGGE GARN AS
NOK 3.6m rev. · NOK −55,000 profit

RYGGE GARN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RYGGE GARN AS

Who owns RYGGE GARN AS?

Camilla Schilling Tønnesen is the largest registered owner, with 50.0%.

What is the revenue of RYGGE GARN AS?

RYGGE GARN AS had revenue of NOK 3.6m in 2025.

Who is the general manager of RYGGE GARN AS?

Camilla Schilling Tønnesen is registered as general manager of RYGGE GARN AS.

Where is RYGGE GARN AS based?

RYGGE GARN AS has its business address in Moss.

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.