biztrac. BETA
COMPANY REGISTER PROFILE
928091015 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

BILISTIC AS

Org. no. 928091015 Limited company (AS) Fredrikstad Incorporated 2021 Active
Revenue 2025 NOK 14.8m
Operating profit NOK 283,000
Equity NOK 494,000
Incorporated 2021
Share capital NOK 300,000

Signals

1 flags
  • Nylig endring 2026-04-27 Adresseendring registrert 2026-04-27.

BILISTIC AS is registered as a limited company in Fredrikstad, Østfold with organisation number 928091015. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2021. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Kjøp og salg av biler. Selskapet skal også kunne drive og delta i andre virksomheter med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.8m in revenue and NOK 283,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.8m
▼ −3 %
Operating profit
NOK 283,000
▼ −59 %
Equity
NOK 494,000
▼ −36 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
2.59
Very good
Current assets ÷ current liabilities
Profitability
8.5%
Satisfactory
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns BILISTIC AS?

BILISTIC AS
NOK 14.8m rev. · NOK 283,000 profit

BILISTIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILISTIC AS

Who owns BILISTIC AS?

Kristoffer Westfalen Helmersen is the largest registered owner, with 100.0%.

What is the revenue of BILISTIC AS?

BILISTIC AS had revenue of NOK 14.8m in 2025.

Who is the general manager of BILISTIC AS?

Kristoffer Westfalen Helmersen is registered as general manager of BILISTIC AS.

Where is BILISTIC AS based?

BILISTIC AS has its business address in Fredrikstad.

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

Report a problem

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