BIZTRAC BETA
Rental and operating of own or leased real estate

SLUPPENVEGEN 11 OG 13 AS

Org. no. 917188653 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 12.6m
Operating profit NOK 5.8m
Equity NOK 36.2m
Incorporated 2016
Share capital NOK 94,000

Signals

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

SLUPPENVEGEN 11 OG 13 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917188653. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 94,000, divided into 100 shares. The company's stated purpose is: “Å eie, forvalte og utvikle egne eiendommer eller ved eierskap i andre selskaper, samt lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.6m in revenue and NOK 5.8m in operating profit.

Key figures · 2024

Revenue
NOK 12.6m
Operating profit
NOK 5.8m
Equity
NOK 36.2m
Est. value
NOK 36.5m

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.2%
Very good
Equity as a share of total capital

Who owns SLUPPENVEGEN 11 OG 13 AS?

R KJELDSBERG AS
SLUPPENVEGEN 11 OG 13 AS
NOK 12.6m rev. · NOK 5.8m profit

SLUPPENVEGEN 11 OG 13 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLUPPENVEGEN 11 OG 13 AS

Who owns SLUPPENVEGEN 11 OG 13 AS?

R KJELDSBERG AS is the largest registered owner, with 100.0%.

What is the revenue of SLUPPENVEGEN 11 OG 13 AS?

SLUPPENVEGEN 11 OG 13 AS had revenue of NOK 12.6m in 2024.

Where is SLUPPENVEGEN 11 OG 13 AS based?

SLUPPENVEGEN 11 OG 13 AS has its business address in Trondheim.

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.