BIZTRAC BETA
Education at other colleges

LIMPI AS

Org. no. 915152503 Limited company (AS) Lillehammer Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 14.4m
Operating profit NOK −1.5m
Equity NOK −2.0m
Incorporated 2015
Employees 6
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

LIMPI AS is registered as a limited company in Lillehammer, Innlandet with organisation number 915152503. The business is classified under education at other colleges (NACE 85.403). The company was incorporated in 2015 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Opplæring og utdanning innen musikk og musikkbransjefag og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.4m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 14.4m
Operating profit
NOK −1.5m
Equity
NOK −2.0m

Financial health · 2024

Liquidity
0.70
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.6%
Weak
Equity as a share of total capital

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

Who owns LIMPI AS?

REELBEATS AS
LIMPI AS
NOK 14.4m rev. · NOK −1.5m profit

LIMPI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIMPI AS

Who owns LIMPI AS?

REELBEATS AS is the largest registered owner, with 100.0%.

What is the revenue of LIMPI AS?

LIMPI AS had revenue of NOK 14.4m in 2024.

Who is the general manager of LIMPI AS?

Magnus Torkehagen Beite is registered as general manager of LIMPI AS.

Where is LIMPI AS based?

LIMPI AS has its business address in Lillehammer.

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.