biztrac. BETA
COMPANY REGISTER PROFILE
985266840 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

NANNA AS

Org. no. 985266840 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK −234,000
Equity NOK 1.2m
Incorporated 2002
Employees 8
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−234k kr).

NANNA AS is registered as a limited company in Oslo, Oslo with organisation number 985266840. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2002 and has 8 registered employees. Registered share capital is NOK 200,000, divided into 100000 shares. The company's stated purpose is: “Handel med moteklær og tilbehør og annen tilknyttet virksomhet derunder å delta i annet selskap med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK −234,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
▼ −18 %
Operating profit
NOK −234,000
▲ +57 %
Equity
NOK 1.2m
▼ −17 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
2.04
Very good
Current assets ÷ current liabilities
Profitability
-6.7%
Not satisfactory
Return on total assets
Solidity
45.8%
Very good
Equity as a share of total capital

Who owns NANNA AS?

NANNA AS
NOK 12.0m rev. · NOK −234,000 profit

NANNA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NANNA AS

Who owns NANNA AS?

NANNA INVEST AS is the largest registered owner, with 66.7%.

What is the revenue of NANNA AS?

NANNA AS had revenue of NOK 12.0m in 2025.

Who is the general manager of NANNA AS?

Nanna-Christine Ebbing Eskevik is registered as general manager of NANNA AS.

Where is NANNA AS based?

NANNA AS has its business address in Oslo.

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.