biztrac. BETA
COMPANY REGISTER PROFILE
931760475 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠GET BACKLINE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Rental and leasing of other personal and household goods

GET BACKLINE AS

Org. no. 931760475 Limited company (AS) Drammen Incorporated 2023 In liquidation
Ownership graph ↗
Revenue 2025 NOK 313,000
Operating profit NOK 242,000
Equity NOK 305,000
Incorporated 2023
Share capital NOK 80,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

GET BACKLINE AS is registered as a limited company in Drammen, Buskerud with organisation number 931760475. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2023. Registered share capital is NOK 80,000, divided into 80000 shares. The company's stated purpose is: “Utleie av musikkinstrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 313,000 in revenue and NOK 242,000 in operating profit.

Key figures · 2025

Revenue
NOK 313,000
▲ +2278 %
Operating profit
NOK 242,000
▲ +2646 %
Equity
NOK 305,000
▲ +381 %

Financial health · 2025

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

Who owns GET BACKLINE AS?

GET BACKLINE AS
NOK 313,000 rev. · NOK 242,000 profit

GET BACKLINE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GET BACKLINE AS

Who owns GET BACKLINE AS?

Tor Erik Fredheim is the largest registered owner, with 75.0%.

What is the revenue of GET BACKLINE AS?

GET BACKLINE AS had revenue of NOK 313,000 in 2025.

Where is GET BACKLINE AS based?

GET BACKLINE AS has its business address in Krokstadelva.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.