BIZTRAC BETA
Business and other management consultancy activities

LAYERTWO AS

Org. no. 934029879 Limited company (AS) Ullensaker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 420,000
Equity NOK 290,000
Incorporated 2024
Share capital NOK 30,000

LAYERTWO AS is registered as a limited company in Ullensaker, Akershus with organisation number 934029879. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulenttjenester, eiendomsutvikling og investering i fast eiendom mm, herunder gjennom aksjetegning eller på annen måte delta i andre selskaper eller foretak som driver lignende virksomhet. Selskapet skal også drive med foredragsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 420,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 420,000
Equity
NOK 290,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns LAYERTWO AS?

KNUT WILHELM HJELMERVIK
LAYERTWO AS
NOK 1.6m rev. · NOK 420,000 profit

LAYERTWO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAYERTWO AS

Who owns LAYERTWO AS?

KNUT WILHELM HJELMERVIK is the largest registered owner, with 100.0%.

What is the revenue of LAYERTWO AS?

LAYERTWO AS had revenue of NOK 1.6m in 2025.

Who is the general manager of LAYERTWO AS?

Knut Wilhelm Hjelmervik is registered as general manager of LAYERTWO AS.

Where is LAYERTWO AS based?

LAYERTWO AS has its business address in Jessheim.

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.