BIZTRAC BETA
COMPANY REGISTER PROFILE
930839124 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

SLÅTTSVEVEGEN 61 AS

Org. no. 930839124 Limited company (AS) Ringsaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 294,000
Operating profit NOK 42,000
Equity NOK −1.0m
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,0 mill kr).

SLÅTTSVEVEGEN 61 AS is registered as a limited company in Ringsaker, Innlandet with organisation number 930839124. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling, utleie, forvaltning og drift av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 294,000 in revenue and NOK 42,000 in operating profit.

Key figures · 2025

Revenue
NOK 294,000
Operating profit
NOK 42,000
Equity
NOK −1.0m
Est. value
NOK 285,000

Financial health · 2025

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

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

Who owns SLÅTTSVEVEGEN 61 AS?

SLÅTTSVEVEGEN 61 AS
NOK 294,000 rev. · NOK 42,000 profit

SLÅTTSVEVEGEN 61 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLÅTTSVEVEGEN 61 AS

Who owns SLÅTTSVEVEGEN 61 AS?

KPN UTVIKLING AS is the largest registered owner, with 60.0%.

What is the revenue of SLÅTTSVEVEGEN 61 AS?

SLÅTTSVEVEGEN 61 AS had revenue of NOK 294,000 in 2025.

Where is SLÅTTSVEVEGEN 61 AS based?

SLÅTTSVEVEGEN 61 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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.