BIZTRAC BETA
Industrial product and fashion design activities

LL&G AS

Org. no. 934196066 Limited company (AS) Lunner Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 14,000
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

LL&G AS is registered as a limited company in Lunner, Akershus with organisation number 934196066. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen industridesign - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 14,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 14,000
Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 26,000

Financial health · 2024

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

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

Who owns LL&G AS?

ARNE OLAV STENERSEN
LL&G AS
NOK 14,000 rev. · NOK −7,000 profit

LL&G AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LL&G AS

Who owns LL&G AS?

ARNE OLAV STENERSEN is the largest registered owner, with 100.0%.

What is the revenue of LL&G AS?

LL&G AS had revenue of NOK 14,000 in 2024.

Who is the general manager of LL&G AS?

Arne Olav Stenersen is registered as general manager of LL&G AS.

Where is LL&G AS based?

LL&G AS has its business address in Lunner.

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.