BIZTRAC BETA
Combined facilities support activities

LEC SERVICE AS

Org. no. 927240327 Limited company (AS) Aurskog-Høland Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 630,000
Operating profit NOK 101,000
Equity NOK 122,000
Incorporated 2021
Share capital NOK 30,000

LEC SERVICE AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 927240327. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Vaktmestertjenester. Snekkerarbeid, montering av dører, vinduer, kjøkken med mer. Rengjøring av bygninger, bolighus, kontorer og lignende, og annen virksomhet som står i naturlig tilknytning til dette. Skifte av filter, service på kulde- og varmepumpeanlegg, herunder ventilasjonsanlegg, og annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 630,000 in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 630,000
Operating profit
NOK 101,000
Equity
NOK 122,000
Est. value
NOK 426,000

Financial health · 2025

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

Who owns LEC SERVICE AS?

LE&C INVEST AS
LEC SERVICE AS
NOK 630,000 rev. · NOK 101,000 profit

LEC SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEC SERVICE AS

Who owns LEC SERVICE AS?

LE&C INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LEC SERVICE AS?

LEC SERVICE AS had revenue of NOK 630,000 in 2025.

Where is LEC SERVICE AS based?

LEC SERVICE AS has its business address in Bjørkelangen.

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.