BIZTRAC BETA
Wholesale of other food

LONGERLIFE NORGE AS

Org. no. 933226573 Limited company (AS) Lillehammer Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 140,000
Operating profit NOK −179,000
Equity NOK −166,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−166k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−179k kr).

LONGERLIFE NORGE AS is registered as a limited company in Lillehammer, Innlandet with organisation number 933226573. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, utvikling, import og salg av hud- og helseprodukter, herunder kjøp, import og salg av utvalgte næringsmidler, samt tilhørende tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 140,000 in revenue and NOK −179,000 in operating profit.

Key figures · 2024

Revenue
NOK 140,000
Operating profit
NOK −179,000
Equity
NOK −166,000

Financial health · 2024

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

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

Who owns LONGERLIFE NORGE AS?

THOMAS HEXEBERG
LONGERLIFE NORGE AS
NOK 140,000 rev. · NOK −179,000 profit

LONGERLIFE NORGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LONGERLIFE NORGE AS

Who owns LONGERLIFE NORGE AS?

THOMAS HEXEBERG is the largest registered owner, with 98.0%.

What is the revenue of LONGERLIFE NORGE AS?

LONGERLIFE NORGE AS had revenue of NOK 140,000 in 2024.

Where is LONGERLIFE NORGE AS based?

LONGERLIFE NORGE 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.