BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

FREKI AS

Org. no. 887254702 Limited company (AS) Øvre Eiker Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 277,000
Operating profit NOK 164,000
Equity NOK −334,000
Incorporated 2004
Share capital NOK 442,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−334k kr).

FREKI AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 887254702. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2004. Registered share capital is NOK 442,000, divided into 442 shares. The company's stated purpose is: “Drift av butikk, investeringer i og handel med aksjer eller andre verdipapirer, samt konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 277,000 in revenue and NOK 164,000 in operating profit.

Key figures · 2024

Revenue
NOK 277,000
Operating profit
NOK 164,000
Equity
NOK −334,000
Est. value
NOK 745,000

Financial health · 2024

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-57.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FREKI AS?

PÅL STIAN DYBDAL
FREKI AS
NOK 277,000 rev. · NOK 164,000 profit

FREKI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FREKI AS

Who owns FREKI AS?

PÅL STIAN DYBDAL is the largest registered owner, with 93.2%.

What is the revenue of FREKI AS?

FREKI AS had revenue of NOK 277,000 in 2024.

Who is the general manager of FREKI AS?

Pål Stian Dybdal is registered as general manager of FREKI AS.

Where is FREKI AS based?

FREKI AS has its business address in Skotselv.

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.