BIZTRAC BETA
General medical practice activities

LOSBYVEIEN LEGESENTER AS

Org. no. 997831977 Limited company (AS) Lørenskog Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −4,000
Equity NOK 1.4m
Incorporated 2011
Employees 6
Share capital NOK 31,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).

LOSBYVEIEN LEGESENTER AS is registered as a limited company in Lørenskog, Akershus with organisation number 997831977. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 31,000, divided into 1020 shares. The company's stated purpose is: “Legesenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −4,000
Equity
NOK 1.4m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns LOSBYVEIEN LEGESENTER AS?

MAELYN IGNACIO TORRES
LOSBYVEIEN LEGESENTER AS
NOK 4.3m rev. · NOK −4,000 profit

LOSBYVEIEN LEGESENTER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOSBYVEIEN LEGESENTER AS

Who owns LOSBYVEIEN LEGESENTER AS?

MAELYN IGNACIO TORRES is the largest registered owner, with 25.0%.

What is the revenue of LOSBYVEIEN LEGESENTER AS?

LOSBYVEIEN LEGESENTER AS had revenue of NOK 4.3m in 2024.

Who is the general manager of LOSBYVEIEN LEGESENTER AS?

Ingunn Landmark is registered as general manager of LOSBYVEIEN LEGESENTER AS.

Where is LOSBYVEIEN LEGESENTER AS based?

LOSBYVEIEN LEGESENTER AS has its business address in Finstadjordet.

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.