BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

MIKAEL SOLLI AS

Org. no. 918459243 Limited company (AS) Bodø Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 148.7m
Operating profit NOK 1.2m
Equity NOK 2.4m
Incorporated 2017
Employees 38
Share capital NOK 500,000

MIKAEL SOLLI AS is registered as a limited company in Bodø, Nordland with organisation number 918459243. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2017 and has 38 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjenom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 148.7m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 148.7m
Operating profit
NOK 1.2m
Equity
NOK 2.4m
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.1%
Satisfactory
Equity as a share of total capital

Who owns MIKAEL SOLLI AS?

MIKAEL SOLLI
MIKAEL SOLLI AS
NOK 148.7m rev. · NOK 1.2m profit

MIKAEL SOLLI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIKAEL SOLLI AS

Who owns MIKAEL SOLLI AS?

MIKAEL SOLLI is the largest registered owner, with 100.0%.

What is the revenue of MIKAEL SOLLI AS?

MIKAEL SOLLI AS had revenue of NOK 148.7m in 2025.

Who is the general manager of MIKAEL SOLLI AS?

Mikael Solli is registered as general manager of MIKAEL SOLLI AS.

Where is MIKAEL SOLLI AS based?

MIKAEL SOLLI AS has its business address in Bodø.

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.