BIZTRAC BETA
General cleaning of buildings

NERLATA AS

Org. no. 928745279 Limited company (AS) Nannestad Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 745,000
Operating profit NOK −56,000
Equity NOK −93,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−93k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−56k kr).

NERLATA AS is registered as a limited company in Nannestad, Akershus with organisation number 928745279. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Renhold, flyttetjenester for private, arbeid utendørs, maling og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 745,000 in revenue and NOK −56,000 in operating profit.

Key figures · 2025

Revenue
NOK 745,000
Operating profit
NOK −56,000
Equity
NOK −93,000

Financial health · 2025

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

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

Who owns NERLATA AS?

NERINGA LATAKIENE
NERLATA AS
NOK 745,000 rev. · NOK −56,000 profit

NERLATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NERLATA AS

Who owns NERLATA AS?

NERINGA LATAKIENE is the largest registered owner, with 100.0%.

What is the revenue of NERLATA AS?

NERLATA AS had revenue of NOK 745,000 in 2025.

Who is the general manager of NERLATA AS?

Neringa Latakiene is registered as general manager of NERLATA AS.

Where is NERLATA AS based?

NERLATA AS has its business address in Holter.

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.