BIZTRAC BETA
COMPANY REGISTER PROFILE
914200733 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

FYLI AS

Org. no. 914200733 Limited company (AS) Vik Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 1.3m
Incorporated 2014
Share capital NOK 30,000

Signals

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

FYLI AS is registered as a limited company in Vik, Vestland with organisation number 914200733. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å investere i aksjer. Selskapet kan også investere i eiendom.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −2 %
Equity
NOK 1.3m
▲ +7044 %
Est. value
NOK 13.9m

Financial health · 2025

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

Who owns FYLI AS?

FYLI AS
· NOK −8,000 profit

FYLI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FYLI AS own?

FYLI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FYLI AS

Who owns FYLI AS?

JANICKE TENOLD REFSDAL is the largest registered owner, with 100.0%.

Where is FYLI AS based?

FYLI AS has its business address in Vik I Sogn.

Property

Business address Seljadalsvegen 144, 6893 Vik I Sogn
Cadastral unit 4639-6/1/0/0
Building Våningshus · 1 unit

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.