BIZTRAC BETA
Rental and operating of own or leased real estate

RINGSAKERVEGEN 11/13 AS

Org. no. 913782631 Limited company (AS) Ringsaker Incorporated 1973 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 1.9m
Equity NOK 5.4m
Incorporated 1973
Share capital NOK 1.5m

Signals

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

RINGSAKERVEGEN 11/13 AS is registered as a limited company in Ringsaker, Innlandet with organisation number 913782631. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1973. Registered share capital is NOK 1.5m, divided into 3000 shares. The company's stated purpose is: “Handel, eie og drive faste eiendommer og hva der- med står i forbindelse, samt ved aksjetegning eller på annen måte å gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 1.9m
Equity
NOK 5.4m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns RINGSAKERVEGEN 11/13 AS?

VIRE AS
RINGSAKERVEGEN 11/13 AS
NOK 2.9m rev. · NOK 1.9m profit

RINGSAKERVEGEN 11/13 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGSAKERVEGEN 11/13 AS

Who owns RINGSAKERVEGEN 11/13 AS?

VIRE AS is the largest registered owner, with 100.0%.

What is the revenue of RINGSAKERVEGEN 11/13 AS?

RINGSAKERVEGEN 11/13 AS had revenue of NOK 2.9m in 2025.

Where is RINGSAKERVEGEN 11/13 AS based?

RINGSAKERVEGEN 11/13 AS has its business address in Brumunddal.

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.