BIZTRAC BETA
Development of building projects

RYE STRAND AS

Org. no. 984571100 Limited company (AS) Risør Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 2.0m
Equity NOK −279,000
Incorporated 2002
Share capital NOK 100,000

Signals

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

RYE STRAND AS is registered as a limited company in Risør, Agder with organisation number 984571100. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utbygging av infrastruktur/fellesanlegg/hytter og salg av hyttetomter på eiendommer Bommyr, gnr 27 bnr 16 i Risør og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 2.0m
Equity
NOK −279,000
Est. value
NOK 15.7m

Financial health · 2024

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

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

Who owns RYE STRAND AS?

FRITZ RYE-ANDERSEN
RYE STRAND AS
NOK 5.3m rev. · NOK 2.0m profit

RYE STRAND AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RYE STRAND AS

Who owns RYE STRAND AS?

FRITZ RYE-ANDERSEN is the largest registered owner, with 50.0%.

What is the revenue of RYE STRAND AS?

RYE STRAND AS had revenue of NOK 5.3m in 2024.

Who is the general manager of RYE STRAND AS?

Fritz Rye-Andersen is registered as general manager of RYE STRAND AS.

Where is RYE STRAND AS based?

RYE STRAND AS has its business address in Søndeled.

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.