BIZTRAC BETA
Industrial product and fashion design activities

BLOFELD VISUALS AS

Org. no. 917911371 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 462,000
Equity NOK 1.6m
Incorporated 2016
Share capital NOK 30,000

BLOFELD VISUALS AS is registered as a limited company in Bærum, Akershus with organisation number 917911371. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av konsulenttjenester innen visualisering, design, kunst, foto, film og reklame, samt annen virksomhet som naturlig faller innunder selskapets virksomhetsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 462,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 462,000
Equity
NOK 1.6m
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
2.73
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.1%
Very good
Equity as a share of total capital

Who owns BLOFELD VISUALS AS?

WILLIAM STENEHJEM BLOFELD
BLOFELD VISUALS AS
NOK 2.9m rev. · NOK 462,000 profit

BLOFELD VISUALS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOFELD VISUALS AS

Who owns BLOFELD VISUALS AS?

WILLIAM STENEHJEM BLOFELD is the largest registered owner, with 100.0%.

What is the revenue of BLOFELD VISUALS AS?

BLOFELD VISUALS AS had revenue of NOK 2.9m in 2024.

Who is the general manager of BLOFELD VISUALS AS?

William Stenehjem Blofeld is registered as general manager of BLOFELD VISUALS AS.

Where is BLOFELD VISUALS AS based?

BLOFELD VISUALS AS has its business address in Lysaker.

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.