BIZTRAC BETA
Joinery installation

FROGNER DØRER AS

Org. no. 931565818 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 549,000
Equity NOK 529,000
Incorporated 2023
Share capital NOK 30,000

FROGNER DØRER AS is registered as a limited company in Oslo, Oslo with organisation number 931565818. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøpe og selge dører, vinduer, byggevarer, agentur og engros, og import av byggevarer, i hovedsak dører, vinduer og tilbehør, samt deltagelse i andre selskap med lignende virksomhet. Videre skal selskapets virksomhet kunne være - direkte eller indirekte - å anskaffe, prosjektere, utbygge, eie, drive, leie ut og selge fast eiendom og alt som er beslektet eller står i forbindelse med slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 549,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 549,000
Equity
NOK 529,000
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns FROGNER DØRER AS?

DALDORFF HOLDING AS
FROGNER DØRER AS
NOK 7.0m rev. · NOK 549,000 profit

FROGNER DØRER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROGNER DØRER AS

Who owns FROGNER DØRER AS?

DALDORFF HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FROGNER DØRER AS?

FROGNER DØRER AS had revenue of NOK 7.0m in 2024.

Where is FROGNER DØRER AS based?

FROGNER DØRER 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 15.06.2026.

Report a problem

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