BIZTRAC BETA
Rental and operating of own or leased real estate

RYPEVEIEN 16 AS

Org. no. 925146471 Limited company (AS) Elverum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 840,000
Operating profit NOK 402,000
Equity NOK −37,000
Incorporated 2020
Share capital NOK 222,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−37k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RYPEVEIEN 16 AS is registered as a limited company in Elverum, Innlandet with organisation number 925146471. 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 222,000, divided into 22216 shares. The company's stated purpose is: “Eiendomsdrift samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 840,000 in revenue and NOK 402,000 in operating profit.

Key figures · 2024

Revenue
NOK 840,000
Operating profit
NOK 402,000
Equity
NOK −37,000
Est. value
NOK 1.9m

Financial health · 2024

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

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

Who owns RYPEVEIEN 16 AS?

NETCO HOLDING AS
RYPEVEIEN 16 AS
NOK 840,000 rev. · NOK 402,000 profit

RYPEVEIEN 16 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYPEVEIEN 16 AS

Who owns RYPEVEIEN 16 AS?

NETCO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RYPEVEIEN 16 AS?

RYPEVEIEN 16 AS had revenue of NOK 840,000 in 2024.

Where is RYPEVEIEN 16 AS based?

RYPEVEIEN 16 AS has its business address in Elverum.

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.