biztrac. BETA
COMPANY REGISTER PROFILE
895712442 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠NELLI 52 AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

NELLI 52 AS

Org. no. 895712442 Limited company (AS) Øygarden Incorporated 2010 In liquidation
Ownership graph ↗
Revenue 2025 NOK 226,000
Operating profit NOK −468,000
Equity NOK 747,000
Incorporated 2010
Share capital NOK 100,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−468k kr).

NELLI 52 AS is registered as a limited company in Øygarden, Vestland with organisation number 895712442. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Holdingselskap, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 226,000 in revenue and NOK −468,000 in operating profit.

Former names: TØMRER OG GÅRDSERVICE AS

Key figures · 2025

Revenue
NOK 226,000
▼ −82 %
Operating profit
NOK −468,000
▼ −60 %
Equity
NOK 747,000
▼ −38 %

Financial health · 2025

Liquidity
7.78
Very good
Current assets ÷ current liabilities
Profitability
-42.0%
Not satisfactory
Return on total assets
Solidity
87.8%
Very good
Equity as a share of total capital

Who owns NELLI 52 AS?

NELLI 52 AS
NOK 226,000 rev. · NOK −468,000 profit

NELLI 52 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NELLI 52 AS

Who owns NELLI 52 AS?

Yngve Lie is the largest registered owner, with 100.0%.

What is the revenue of NELLI 52 AS?

NELLI 52 AS had revenue of NOK 226,000 in 2025.

Where is NELLI 52 AS based?

NELLI 52 AS has its business address in Kolltveit.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.