biztrac. BETA
COMPANY REGISTER PROFILE
919557966 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

FJELLWEB AS

Org. no. 919557966 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 58,000
Operating profit NOK 23,000
Equity NOK 56,000
Incorporated 2017
Share capital NOK 30,000

FJELLWEB AS is registered as a limited company in Bergen, Vestland with organisation number 919557966. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Webdesign, nettbutikksystemer, programmering og mediebyråtjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 58,000 in revenue and NOK 23,000 in operating profit.

Former names: KODEBOX AS

Key figures · 2025

Revenue
NOK 58,000
▼ −0 %
Operating profit
NOK 23,000
▲ +1 %
Equity
NOK 56,000
▲ +12 %
Est. value
NOK 107,000

Financial health · 2025

Liquidity
2.65
Very good
Current assets ÷ current liabilities
Profitability
30.1%
Very good
Return on total assets
Solidity
62.3%
Weak
Equity as a share of total capital

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

Who owns FJELLWEB AS?

FJELLWEB AS
NOK 58,000 rev. · NOK 23,000 profit

FJELLWEB AS has 2 registered shareholders:

All shareholders and roles →

Group structure

FJELLWEB AS er morselskap for 1 datterselskap:

Frequently asked questions about FJELLWEB AS

Who owns FJELLWEB AS?

KARBONADE AS is the largest registered owner, with 50.0%.

What is the revenue of FJELLWEB AS?

FJELLWEB AS had revenue of NOK 58,000 in 2025.

Who is the general manager of FJELLWEB AS?

Kim Bjarte Bruland is registered as general manager of FJELLWEB AS.

Where is FJELLWEB AS based?

FJELLWEB AS has its business address in Nesttun.

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.