BIZTRAC BETA
COMPANY REGISTER PROFILE
913571932 ORG. NO. 2017 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Activities of tourist offices and destination marketing organisations

FLÅ VEKST SA

Org. no. 913571932 Co-operation (SA) Flå Incorporated 2014 Active
Ownership graph ↗
Revenue 2017 NOK 851,000
Operating profit NOK 28,000
Equity NOK 406,000
Incorporated 2014

FLÅ VEKST SA is registered as a co-operation in Flå, Buskerud with organisation number 913571932. The business is classified under activities of tourist offices and destination marketing organisations (NACE 79.901). The company was incorporated in 2014. The company's stated purpose is: “Utvikle, koordinere og synliggjøre næringsliv, reiselivstilbud og øvrige næringsaktiviteter for medlemmene i Flå kommune, og derigjennom fremme medlemmenes økonomiske interesser.”. The most recent filed accounts, for the 2017 financial year, show NOK 851,000 in revenue and NOK 28,000 in operating profit.

Former names: VISIT FLÅ SA

Key figures · 2017

Revenue
NOK 851,000
Operating profit
NOK 28,000
Equity
NOK 406,000
Est. value
NOK 358,000

Financial health · 2017

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

Who owns FLÅ VEKST SA?

No shareholders are registered for FLÅ VEKST SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does FLÅ VEKST SA own?

FLÅ VEKST SA holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FLÅ VEKST SA

What is the revenue of FLÅ VEKST SA?

FLÅ VEKST SA had revenue of NOK 851,000 in 2017.

Who is the general manager of FLÅ VEKST SA?

Tor Egil Buøen is registered as general manager of FLÅ VEKST SA.

Where is FLÅ VEKST SA based?

FLÅ VEKST SA has its business address in Flå.

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

Report a problem

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