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

MØBELRINGEN FOLLO AS

Org. no. 914991331 Limited company (AS) Ås Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 56.9m
Operating profit NOK 8.0m
Equity NOK 1.7m
Incorporated 2014
Employees 13
Share capital NOK 500,000

MØBELRINGEN FOLLO AS is registered as a limited company in Ås, Akershus with organisation number 914991331. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 2014 and has 13 registered employees. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Handel med møbler og tilhørende produkter samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 56.9m in revenue and NOK 8.0m in operating profit.

Key figures · 2024

Revenue
NOK 56.9m
Operating profit
NOK 8.0m
Equity
NOK 1.7m
Est. value
NOK 25.0m

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns MØBELRINGEN FOLLO AS?

VAAGEN OG KROGSRUD HOLDING AS
MØBELRINGEN FOLLO AS
NOK 56.9m rev. · NOK 8.0m profit

MØBELRINGEN FOLLO AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MØBELRINGEN FOLLO AS own?

MØBELRINGEN FOLLO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MØBELRINGEN FOLLO AS

Who owns MØBELRINGEN FOLLO AS?

VAAGEN OG KROGSRUD HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of MØBELRINGEN FOLLO AS?

MØBELRINGEN FOLLO AS had revenue of NOK 56.9m in 2024.

Where is MØBELRINGEN FOLLO AS based?

MØBELRINGEN FOLLO AS has its business address in Vinterbro.

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.