BIZTRAC BETA
Retail sale of furniture, including mattresses and box springs

FAGMØBLER BUTIKKER AS

Org. no. 934243528 Limited company (AS) Gloppen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −422
Equity NOK 6.9m
Incorporated 2024
Share capital NOK 106,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−422 kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FAGMØBLER BUTIKKER AS is registered as a limited company in Gloppen, Vestland with organisation number 934243528. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 2024. Registered share capital is NOK 106,000, divided into 5310 shares. The company's stated purpose is: “Å eie aksjer i Fagmøbler Norge AS og evt. andre selskaper, samt andre aktiviteter som måtte følge av dette.”.

Key figures · 2024

Operating profit
NOK −422
Equity
NOK 6.9m
Est. value
NOK 8.7m

Financial health · 2024

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

Who owns FAGMØBLER BUTIKKER AS?

FAGMØBLER BUTIKKER AS
FAGMØBLER BUTIKKER AS
· NOK −422 profit

FAGMØBLER BUTIKKER AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does FAGMØBLER BUTIKKER AS own?

FAGMØBLER BUTIKKER AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

FAGMØBLER BUTIKKER AS er morselskap for 1 datterselskap:

Frequently asked questions about FAGMØBLER BUTIKKER AS

Who owns FAGMØBLER BUTIKKER AS?

FAGMØBLER BUTIKKER AS is the largest registered owner, with 5.1%.

Where is FAGMØBLER BUTIKKER AS based?

FAGMØBLER BUTIKKER AS has its business address in Sandane.

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.