BIZTRAC BETA
Beauty care and other beauty treatment activities

SPASPA BY MIKKELBORG AVD. KANEBOGEN

Org. no. 913941446 Limited company (AS) Harstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 107,000
Equity NOK 1.4m
Incorporated 2014
Employees 5
Share capital NOK 50,000

SPASPA BY MIKKELBORG AVD. KANEBOGEN is registered as a limited company in Harstad, Troms with organisation number 913941446. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Fremstilling/salg av hudpleieprodukter og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 107,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 107,000
Equity
NOK 1.4m
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.92
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.5%
Very good
Equity as a share of total capital

Who owns SPASPA BY MIKKELBORG AVD. KANEBOGEN?

SPASPA BY MIKKELBORG AS
SPASPA BY MIKKELBORG AVD. KANEBOGEN
NOK 4.2m rev. · NOK 107,000 profit

SPASPA BY MIKKELBORG AVD. KANEBOGEN has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPASPA BY MIKKELBORG AVD. KANEBOGEN

Who owns SPASPA BY MIKKELBORG AVD. KANEBOGEN?

SPASPA BY MIKKELBORG AS is the largest registered owner, with 100.0%.

What is the revenue of SPASPA BY MIKKELBORG AVD. KANEBOGEN?

SPASPA BY MIKKELBORG AVD. KANEBOGEN had revenue of NOK 4.2m in 2025.

Where is SPASPA BY MIKKELBORG AVD. KANEBOGEN based?

SPASPA BY MIKKELBORG AVD. KANEBOGEN has its business address in Harstad.

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.