BIZTRAC BETA
Rental and operating of own or leased real estate

KJELLINGMOVEIEN 4 AS

Org. no. 932441616 Limited company (AS) Aurskog-Høland Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 2.7m
Equity NOK 347,000
Incorporated 2023
Share capital NOK 30,000

KJELLINGMOVEIEN 4 AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 932441616. 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 30000 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom og alt som står i naturlig forbindelse med dette. Herunder investeringer i foretak som driver slik virksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 2.7m
Equity
NOK 347,000
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Not satisfactory
Equity as a share of total capital

Who owns KJELLINGMOVEIEN 4 AS?

BYGGIMPULS AS
KJELLINGMOVEIEN 4 AS
NOK 4.0m rev. · NOK 2.7m profit

KJELLINGMOVEIEN 4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJELLINGMOVEIEN 4 AS

Who owns KJELLINGMOVEIEN 4 AS?

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

What is the revenue of KJELLINGMOVEIEN 4 AS?

KJELLINGMOVEIEN 4 AS had revenue of NOK 4.0m in 2025.

Who is the general manager of KJELLINGMOVEIEN 4 AS?

Tore Morten Ulvedalen is registered as general manager of KJELLINGMOVEIEN 4 AS.

Where is KJELLINGMOVEIEN 4 AS based?

KJELLINGMOVEIEN 4 AS has its business address in Aurskog.

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.