BIZTRAC BETA
Traditional, complementary and alternative medicine activities

MUSKEL OG LEDD AS

Org. no. 935145104 Limited company (AS) Ringsaker Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 543,000
Operating profit NOK 26,000
Equity NOK 50,000
Incorporated 2025
Share capital NOK 30,000

MUSKEL OG LEDD AS is registered as a limited company in Ringsaker, Innlandet with organisation number 935145104. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Manuell behandling og treningsveiledning med tilhørende varesalg i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 543,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 543,000
Operating profit
NOK 26,000
Equity
NOK 50,000
Est. value
NOK 155,000

Financial health · 2025

Liquidity
2.46
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
59.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MUSKEL OG LEDD AS?

AMANDA LILLEGJENG
MUSKEL OG LEDD AS
NOK 543,000 rev. · NOK 26,000 profit

MUSKEL OG LEDD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MUSKEL OG LEDD AS

Who owns MUSKEL OG LEDD AS?

AMANDA LILLEGJENG is the largest registered owner, with 100.0%.

What is the revenue of MUSKEL OG LEDD AS?

MUSKEL OG LEDD AS had revenue of NOK 543,000 in 2025.

Who is the general manager of MUSKEL OG LEDD AS?

Amanda Lillegjeng is registered as general manager of MUSKEL OG LEDD AS.

Where is MUSKEL OG LEDD AS based?

MUSKEL OG LEDD AS has its business address in Brumunddal.

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.