biztrac. BETA
COMPANY REGISTER PROFILE
936257674 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

RUSELØKKVEIEN 59 SEKSJON 2 AS

Org. no. 936257674 Limited company (AS) Asker Incorporated 2025 Active
Revenue 2025 NOK 867,000
Operating profit NOK 547,000
Equity NOK 110,000
Incorporated 2025
Share capital NOK 30,000

RUSELØKKVEIEN 59 SEKSJON 2 AS is registered as a limited company in Asker, Akershus with organisation number 936257674. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å eie, utvikle, forvalte, kjøpe, selge og leie ut fast eiendom, samt virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 867,000 in revenue and NOK 547,000 in operating profit.

Key figures · 2025

Revenue
NOK 867,000
Operating profit
NOK 547,000
Equity
NOK 110,000
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns RUSELØKKVEIEN 59 SEKSJON 2 AS?

RUSELØKKVEIEN 59 SEKSJON 2 AS
NOK 867,000 rev. · NOK 547,000 profit

RUSELØKKVEIEN 59 SEKSJON 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUSELØKKVEIEN 59 SEKSJON 2 AS

Who owns RUSELØKKVEIEN 59 SEKSJON 2 AS?

MIRJAN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RUSELØKKVEIEN 59 SEKSJON 2 AS?

RUSELØKKVEIEN 59 SEKSJON 2 AS had revenue of NOK 867,000 in 2025.

Where is RUSELØKKVEIEN 59 SEKSJON 2 AS based?

RUSELØKKVEIEN 59 SEKSJON 2 AS has its business address in Billingstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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