BIZTRAC BETA
Rental and operating of own or leased real estate

MYKLEBUST BUTIKKEIENDOM AS

Org. no. 818686722 Limited company (AS) Sola Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.7m
Equity NOK 10.3m
Incorporated 2017
Share capital NOK 45,000

Signals

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

MYKLEBUST BUTIKKEIENDOM AS is registered as a limited company in Sola, Rogaland with organisation number 818686722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 45,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom , samt aktiviteter som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.7m
Equity
NOK 10.3m
Est. value
NOK 9.6m

Financial health · 2024

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

Who owns MYKLEBUST BUTIKKEIENDOM AS?

ALTO INVEST AS
MYKLEBUST BUTIKKEIENDOM AS
NOK 2.2m rev. · NOK 1.7m profit

MYKLEBUST BUTIKKEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYKLEBUST BUTIKKEIENDOM AS

Who owns MYKLEBUST BUTIKKEIENDOM AS?

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

What is the revenue of MYKLEBUST BUTIKKEIENDOM AS?

MYKLEBUST BUTIKKEIENDOM AS had revenue of NOK 2.2m in 2024.

Where is MYKLEBUST BUTIKKEIENDOM AS based?

MYKLEBUST BUTIKKEIENDOM AS has its business address in Tananger.

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.