BIZTRAC BETA
COMPANY REGISTER PROFILE
811665762 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Retail sale of fish, crustaceans and molluscs

O FJELBERG AS

Org. no. 811665762 Limited company (AS) Oslo Incorporated 1917 Active
Ownership graph ↗
Revenue 2025 NOK 29.4m
Operating profit NOK 3.0m
Equity NOK 7.6m
Incorporated 1917
Employees 11
Share capital NOK 100,000

O FJELBERG AS is registered as a limited company in Oslo, Oslo with organisation number 811665762. The business is classified under retail sale of fish, crustaceans and molluscs (NACE 47.230). The company was incorporated in 1917 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Omsetning av delikatesser, samt drift av fast eiendom og investering i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.4m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 29.4m
▲ +7 %
Operating profit
NOK 3.0m
▲ +89 %
Equity
NOK 7.6m
▲ +47 %
Est. value
NOK 13.1m

Financial health · 2025

Liquidity
2.21
Very good
Current assets ÷ current liabilities
Profitability
27.1%
Very good
Return on total assets
Solidity
58.5%
Very good
Equity as a share of total capital

Who owns O FJELBERG AS?

O FJELBERG AS
NOK 29.4m rev. · NOK 3.0m profit

O FJELBERG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

O FJELBERG AS er morselskap for 1 datterselskap:

Frequently asked questions about O FJELBERG AS

Who owns O FJELBERG AS?

VIOL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of O FJELBERG AS?

O FJELBERG AS had revenue of NOK 29.4m in 2025.

Who is the general manager of O FJELBERG AS?

Per-Ole Fjelberg is registered as general manager of O FJELBERG AS.

Where is O FJELBERG AS based?

O FJELBERG AS has its business address in Oslo.

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

Report a problem

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