BIZTRAC BETA
Business and other management consultancy activities

FRONTLYKT AS

Org. no. 911566346 Limited company (AS) Lier Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −5,000
Equity NOK 127,000
Incorporated 2013
Share capital NOK 50,000

Signals

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

FRONTLYKT AS is registered as a limited company in Lier, Buskerud with organisation number 911566346. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Investeringsvirksomhet, direkte eller indirekte deltagelse i selskaper samt det som naturlig står i forbindelse med dette, herunder ulike typer konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −5,000
Equity
NOK 127,000
Est. value
NOK 67,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.5%
Weak
Equity as a share of total capital

Who owns FRONTLYKT AS?

FRIDTJOF BUVARP
FRONTLYKT AS
NOK 5,000 rev. · NOK −5,000 profit

FRONTLYKT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRONTLYKT AS own?

FRONTLYKT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRONTLYKT AS

Who owns FRONTLYKT AS?

FRIDTJOF BUVARP is the largest registered owner, with 100.0%.

What is the revenue of FRONTLYKT AS?

FRONTLYKT AS had revenue of NOK 5,000 in 2025.

Where is FRONTLYKT AS based?

FRONTLYKT AS has its business address in Tranby.

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.