BIZTRAC BETA
Retail sale of clothing

FRØKEN FRØLAND AS

Org. no. 989815865 Limited company (AS) Ålesund Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 153,000
Equity NOK 555,000
Incorporated 2006
Share capital NOK 100,000

FRØKEN FRØLAND AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 989815865. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive butikkhandel med klær og sko og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 153,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 153,000
Equity
NOK 555,000
Est. value
NOK 897,000

Financial health · 2025

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

Who owns FRØKEN FRØLAND AS?

RIGMOR VESTRE
FRØKEN FRØLAND AS
NOK 4.8m rev. · NOK 153,000 profit

FRØKEN FRØLAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRØKEN FRØLAND AS

Who owns FRØKEN FRØLAND AS?

RIGMOR VESTRE is the largest registered owner, with 100.0%.

What is the revenue of FRØKEN FRØLAND AS?

FRØKEN FRØLAND AS had revenue of NOK 4.8m in 2025.

Who is the general manager of FRØKEN FRØLAND AS?

Rigmor Vestre is registered as general manager of FRØKEN FRØLAND AS.

Where is FRØKEN FRØLAND AS based?

FRØKEN FRØLAND AS has its business address in Ålesund.

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.