BIZTRAC BETA
Rental and operating of own or leased real estate

RYGHGATA 6A EIENDOM AS

Org. no. 925573612 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 2.0m
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RYGHGATA 6A EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 925573612. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie, forvalte og utvikle fast eiendom, samt annen virksomhet beslektet med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 2.0m
Equity
NOK 1.6m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns RYGHGATA 6A EIENDOM AS?

DRÅPEN HOLDING AS
RYGHGATA 6A EIENDOM AS
NOK 2.5m rev. · NOK 2.0m profit

RYGHGATA 6A EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYGHGATA 6A EIENDOM AS

Who owns RYGHGATA 6A EIENDOM AS?

DRÅPEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RYGHGATA 6A EIENDOM AS?

RYGHGATA 6A EIENDOM AS had revenue of NOK 2.5m in 2024.

Where is RYGHGATA 6A EIENDOM AS based?

RYGHGATA 6A EIENDOM AS has its business address in Drammen.

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.