BIZTRAC BETA
Industrial product and fashion design activities

NEKKO AS

Org. no. 925015296 Limited company (AS) Frogn Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 70,000
Operating profit NOK −59,000
Equity NOK 195,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

NEKKO AS is registered as a limited company in Frogn, Akershus with organisation number 925015296. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen elektronikk og mekanikkutvikling - 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 70,000 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 70,000
Operating profit
NOK −59,000
Equity
NOK 195,000
Est. value
NOK 168,000

Financial health · 2024

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

Who owns NEKKO AS?

FREDRIK NEROL BEILEGAARD
NEKKO AS
NOK 70,000 rev. · NOK −59,000 profit

NEKKO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEKKO AS

Who owns NEKKO AS?

FREDRIK NEROL BEILEGAARD is the largest registered owner, with 100.0%.

What is the revenue of NEKKO AS?

NEKKO AS had revenue of NOK 70,000 in 2024.

Who is the general manager of NEKKO AS?

Fredrik Nerol Beilegaard is registered as general manager of NEKKO AS.

Where is NEKKO AS based?

NEKKO AS has its business address in Drøbak.

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.