BIZTRAC BETA
Graphic design and visual communication activities

BLOCK HELLUM DESIGN AS

Org. no. 916541031 Limited company (AS) Nesodden Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 28,000
Equity NOK 357,000
Incorporated 2016
Share capital NOK 30,000

BLOCK HELLUM DESIGN AS is registered as a limited company in Nesodden, Akershus with organisation number 916541031. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innenfor formgivning og produktutvikling og annet som naturlig faller sammen med dette, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 28,000
Equity
NOK 357,000
Est. value
NOK 353,000

Financial health · 2025

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

Who owns BLOCK HELLUM DESIGN AS?

MADS BLOCK HELLUM
BLOCK HELLUM DESIGN AS
NOK 1.1m rev. · NOK 28,000 profit

BLOCK HELLUM DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLOCK HELLUM DESIGN AS

Who owns BLOCK HELLUM DESIGN AS?

MADS BLOCK HELLUM is the largest registered owner, with 100.0%.

What is the revenue of BLOCK HELLUM DESIGN AS?

BLOCK HELLUM DESIGN AS had revenue of NOK 1.1m in 2025.

Who is the general manager of BLOCK HELLUM DESIGN AS?

Mads Block Hellum is registered as general manager of BLOCK HELLUM DESIGN AS.

Where is BLOCK HELLUM DESIGN AS based?

BLOCK HELLUM DESIGN AS has its business address in Nesodden.

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.