BIZTRAC BETA
Installation of industrial machinery and equipment

FREN AS

Org. no. 928932966 Limited company (AS) Vestby Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 76,000
Equity NOK 65,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FREN AS is registered as a limited company in Vestby, Akershus with organisation number 928932966. The business is classified under installation of industrial machinery and equipment (NACE 33.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Murverksteknologi med tilhørende tjenester og produkter med fokus på nybygg, service- og vedlikeholdstjenester rettet mot forbrenningsteknologi.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 76,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 76,000
Equity
NOK 65,000
Est. value
NOK 323,000

Financial health · 2024

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

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

Who owns FREN AS?

ILDFAST AS
FREN AS
NOK 6.8m rev. · NOK 76,000 profit

FREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FREN AS

Who owns FREN AS?

ILDFAST AS is the largest registered owner, with 100.0%.

What is the revenue of FREN AS?

FREN AS had revenue of NOK 6.8m in 2024.

Who is the general manager of FREN AS?

Tomasz Sawicki is registered as general manager of FREN AS.

Where is FREN AS based?

FREN AS has its business address in Vestby.

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.