BIZTRAC BETA
COMPANY REGISTER PROFILE
928764230 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

FRESNEL AS

Org. no. 928764230 Limited company (AS) Sør-Varanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −23,000
Equity NOK 58,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).
  • Nylig endring 2026-03-12 Adresseendring registrert 2026-03-12.

FRESNEL AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 928764230. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen IT.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK 58,000
Est. value
NOK 104,000

Financial health · 2025

Liquidity
1.92
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
46.2%
Weak
Equity as a share of total capital

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

Who owns FRESNEL AS?

TOR TRYGGESTAD BERRE
FRESNEL AS
NOK 0 rev. · NOK −23,000 profit

FRESNEL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRESNEL AS

Who owns FRESNEL AS?

TOR TRYGGESTAD BERRE is the largest registered owner, with 50.0%.

What is the revenue of FRESNEL AS?

FRESNEL AS had revenue of NOK 0 in 2025.

Who is the general manager of FRESNEL AS?

Herman Henriksen is registered as general manager of FRESNEL AS.

Where is FRESNEL AS based?

FRESNEL AS has its business address in Kirkenes.

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.