BIZTRAC BETA
Other content distribution activities

THANKS TO BOREDOM AS

Org. no. 919282924 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 17,000
Operating profit NOK 13,000
Equity NOK −428,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−428k kr).

THANKS TO BOREDOM AS is registered as a limited company in Bærum, Akershus with organisation number 919282924. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Reiseliv og sosialt medium.”. The most recent filed accounts, for the 2024 financial year, show NOK 17,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 17,000
Operating profit
NOK 13,000
Equity
NOK −428,000
Est. value
NOK 55,000

Financial health · 2024

Liquidity
25.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-192.1%
Weak
Equity as a share of total capital

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

Who owns THANKS TO BOREDOM AS?

HARALD FREDRIK ZEINER-GUNDERSEN
THANKS TO BOREDOM AS
NOK 17,000 rev. · NOK 13,000 profit

THANKS TO BOREDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THANKS TO BOREDOM AS own?

THANKS TO BOREDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about THANKS TO BOREDOM AS

Who owns THANKS TO BOREDOM AS?

HARALD FREDRIK ZEINER-GUNDERSEN is the largest registered owner, with 100.0%.

What is the revenue of THANKS TO BOREDOM AS?

THANKS TO BOREDOM AS had revenue of NOK 17,000 in 2024.

Where is THANKS TO BOREDOM AS based?

THANKS TO BOREDOM AS has its business address in Jar.

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.