BIZTRAC BETA
Rental and operating of own or leased real estate

KJEPPESTADVEIEN 44 AS

Org. no. 916740212 Limited company (AS) Nordre Follo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 27.1m
Operating profit NOK 17.5m
Equity NOK 16.1m
Incorporated 2016
Share capital NOK 10.0m

Signals

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

KJEPPESTADVEIEN 44 AS is registered as a limited company in Nordre Follo, Akershus with organisation number 916740212. 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 10.0m, divided into 50 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av fast eiendom, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.1m in revenue and NOK 17.5m in operating profit.

Key figures · 2024

Revenue
NOK 27.1m
Operating profit
NOK 17.5m
Equity
NOK 16.1m
Est. value
NOK 43.4m

Financial health · 2024

Liquidity
1.89
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.4%
Good
Equity as a share of total capital

Who owns KJEPPESTADVEIEN 44 AS?

SBG INVEST AS
KJEPPESTADVEIEN 44 AS
NOK 27.1m rev. · NOK 17.5m profit

KJEPPESTADVEIEN 44 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KJEPPESTADVEIEN 44 AS er morselskap for 6 datterselskaper:

Frequently asked questions about KJEPPESTADVEIEN 44 AS

Who owns KJEPPESTADVEIEN 44 AS?

SBG INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KJEPPESTADVEIEN 44 AS?

KJEPPESTADVEIEN 44 AS had revenue of NOK 27.1m in 2024.

Where is KJEPPESTADVEIEN 44 AS based?

KJEPPESTADVEIEN 44 AS has its business address in Ski.

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.