BIZTRAC BETA
Retail sale of clothing

MIABELL UNDERTØYSALONG AS

Org. no. 943122393 Limited company (AS) Kristiansand Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK −2,000
Equity NOK 575,000
Incorporated 1987
Employees 5
Share capital NOK 2.6m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).

MIABELL UNDERTØYSALONG AS is registered as a limited company in Kristiansand, Agder with organisation number 943122393. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1987 and has 5 registered employees. Registered share capital is NOK 2.6m, divided into 1650 shares. The company's stated purpose is: “Handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK −2,000
Equity
NOK 575,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns MIABELL UNDERTØYSALONG AS?

SOFIE MONICA ARONSSON
MIABELL UNDERTØYSALONG AS
NOK 3.4m rev. · NOK −2,000 profit

MIABELL UNDERTØYSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIABELL UNDERTØYSALONG AS

Who owns MIABELL UNDERTØYSALONG AS?

SOFIE MONICA ARONSSON is the largest registered owner, with 100.0%.

What is the revenue of MIABELL UNDERTØYSALONG AS?

MIABELL UNDERTØYSALONG AS had revenue of NOK 3.4m in 2025.

Who is the general manager of MIABELL UNDERTØYSALONG AS?

Sofie Monica Aronsson is registered as general manager of MIABELL UNDERTØYSALONG AS.

Where is MIABELL UNDERTØYSALONG AS based?

MIABELL UNDERTØYSALONG AS has its business address in Kristiansand S.

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.