BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

NO3 DRØBAK AS

Org. no. 816762502 Limited company (AS) Frogn Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.5m
Operating profit NOK −331,000
Equity NOK 757,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

NO3 DRØBAK AS is registered as a limited company in Frogn, Akershus with organisation number 816762502. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av interiør, møbler, nytt og brukt, møbeltapetsering, tjenester innen styling og andre produkter/tjenester son naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.5m in revenue and NOK −331,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.5m
Operating profit
NOK −331,000
Equity
NOK 757,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns NO3 DRØBAK AS?

BETTINA VOGTER NØRREMARK
NO3 DRØBAK AS
NOK 4.5m rev. · NOK −331,000 profit

NO3 DRØBAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NO3 DRØBAK AS

Who owns NO3 DRØBAK AS?

BETTINA VOGTER NØRREMARK is the largest registered owner, with 100.0%.

What is the revenue of NO3 DRØBAK AS?

NO3 DRØBAK AS had revenue of NOK 4.5m in 2024.

Who is the general manager of NO3 DRØBAK AS?

Bettina Vogter Nørremark is registered as general manager of NO3 DRØBAK AS.

Where is NO3 DRØBAK AS based?

NO3 DRØBAK 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.