biztrac. BETA
COMPANY REGISTER PROFILE
918377573 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Industrial product and fashion design activities

FLOR AS

Org. no. 918377573 Limited company (AS) Voss Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK −789,000
Equity NOK 3.4m
Incorporated 2017
Employees 10
Share capital NOK 4.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−789k kr).

FLOR AS is registered as a limited company in Voss, Vestland with organisation number 918377573. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2017 and has 10 registered employees. Registered share capital is NOK 4.2m, divided into 1178018 shares. The company's stated purpose is: “Design, produksjon og sal av klede, og utstyr for arbeid, hage, fritid og til utebruk, samt investering i tilknytte selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK −789,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
▲ +46 %
Operating profit
NOK −789,000
▲ +58 %
Equity
NOK 3.4m
▼ −20 %
Est. value
NOK 9.9m

Financial health · 2025

Liquidity
2.47
Very good
Current assets ÷ current liabilities
Profitability
-11.1%
Not satisfactory
Return on total assets
Solidity
45.3%
Very good
Equity as a share of total capital

Who owns FLOR AS?

FLOR AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about FLOR AS

Who owns FLOR AS?

AGALAUS AS is the largest registered owner, with 27.5%.

What is the revenue of FLOR AS?

FLOR AS had revenue of NOK 8.7m in 2025.

Who is the general manager of FLOR AS?

Kjersti Konglevoll La Motte is registered as general manager of FLOR AS.

Where is FLOR AS based?

FLOR AS has its business address in Voss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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