BIZTRAC BETA
Roofing activities

KJELSÅSVEIEN 170 AS

Org. no. 915626920 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 1.4m
Equity NOK 9.1m
Incorporated 2015
Share capital NOK 460,000

Signals

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

KJELSÅSVEIEN 170 AS is registered as a limited company in Oslo, Oslo with organisation number 915626920. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2015. Registered share capital is NOK 460,000, divided into 100 shares. The company's stated purpose is: “Eie og drive fast eiendom og hva hertil henhører.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 1.4m
Equity
NOK 9.1m
Est. value
NOK 8.3m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.0%
Very good
Equity as a share of total capital

Who owns KJELSÅSVEIEN 170 AS?

FRANKE ONSRUD INVEST AS
KJELSÅSVEIEN 170 AS
NOK 2.1m rev. · NOK 1.4m profit

KJELSÅSVEIEN 170 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KJELSÅSVEIEN 170 AS er morselskap for 3 datterselskaper:

Frequently asked questions about KJELSÅSVEIEN 170 AS

Who owns KJELSÅSVEIEN 170 AS?

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

What is the revenue of KJELSÅSVEIEN 170 AS?

KJELSÅSVEIEN 170 AS had revenue of NOK 2.1m in 2024.

Who is the general manager of KJELSÅSVEIEN 170 AS?

Franke Onsrud is registered as general manager of KJELSÅSVEIEN 170 AS.

Where is KJELSÅSVEIEN 170 AS based?

KJELSÅSVEIEN 170 AS has its business address in Oslo.

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.