BIZTRAC BETA
Graphic design and visual communication activities

HJØRNEBRIKKE AS

Org. no. 935520851 Limited company (AS) Bodø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 59,000
Operating profit NOK −31,000
Equity NOK 12,000
Incorporated 2025
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

HJØRNEBRIKKE AS is registered as a limited company in Bodø, Nordland with organisation number 935520851. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2025. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Utvikling og salg av design- og kommunikasjonstjenester samt tilhørende produkter og eierskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 59,000 in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 59,000
Operating profit
NOK −31,000
Equity
NOK 12,000
Est. value
NOK 68,000

Financial health · 2025

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.5%
Weak
Equity as a share of total capital

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

Who owns HJØRNEBRIKKE AS?

THOMAS LITANGEN
HJØRNEBRIKKE AS
NOK 59,000 rev. · NOK −31,000 profit

HJØRNEBRIKKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJØRNEBRIKKE AS

Who owns HJØRNEBRIKKE AS?

THOMAS LITANGEN is the largest registered owner, with 100.0%.

What is the revenue of HJØRNEBRIKKE AS?

HJØRNEBRIKKE AS had revenue of NOK 59,000 in 2025.

Who is the general manager of HJØRNEBRIKKE AS?

Thomas Litangen is registered as general manager of HJØRNEBRIKKE AS.

Where is HJØRNEBRIKKE AS based?

HJØRNEBRIKKE AS has its business address in Bodø.

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.