BIZTRAC BETA
Sound recording and music publishing activities

BORING AS

Org. no. 931236350 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 21,000
Operating profit NOK 21,000
Equity NOK 66,000
Incorporated 2023
Share capital NOK 30,000

BORING AS is registered as a limited company in Oslo, Oslo with organisation number 931236350. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen plateselskap og virksomhet i underholdningsbransjen og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 21,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2024

Revenue
NOK 21,000
Operating profit
NOK 21,000
Equity
NOK 66,000
Est. value
NOK 112,000

Financial health · 2024

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

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

Who owns BORING AS?

ANDERS KRISTOFFER FOLKEDAL HAJEM
BORING AS
NOK 21,000 rev. · NOK 21,000 profit

BORING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BORING AS

Who owns BORING AS?

ANDERS KRISTOFFER FOLKEDAL HAJEM is the largest registered owner, with 33.3%.

What is the revenue of BORING AS?

BORING AS had revenue of NOK 21,000 in 2024.

Who is the general manager of BORING AS?

Anders Kristoffer Folkedal Hajem is registered as general manager of BORING AS.

Where is BORING AS based?

BORING AS has its business address in Oslo.

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.