BIZTRAC BETA
COMPANY REGISTER PROFILE
994519832 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

LEMONTREE AS

Org. no. 994519832 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −78,000
Equity NOK 323,000
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−78k kr).

LEMONTREE AS is registered as a limited company in Oslo, Oslo with organisation number 994519832. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets virksomhet er import og eksport, salg av IT-løsninger, rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −78,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −78,000
Equity
NOK 323,000
Est. value
NOK 585,000

Financial health · 2025

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

Who owns LEMONTREE AS?

LEMONTREE ENTERPRISE SOLUTIONS AB
LEMONTREE AS
NOK 0 rev. · NOK −78,000 profit

LEMONTREE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEMONTREE AS

Who owns LEMONTREE AS?

LEMONTREE ENTERPRISE SOLUTIONS AB is the largest registered owner, with 100.0%.

What is the revenue of LEMONTREE AS?

LEMONTREE AS had revenue of NOK 0 in 2025.

Who is the general manager of LEMONTREE AS?

Nils Olof Patric Helje is registered as general manager of LEMONTREE AS.

Where is LEMONTREE AS based?

LEMONTREE AS has its business address in Oslo.

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.