biztrac. BETA
COMPANY REGISTER PROFILE
989240099 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

BALLOGLASTER AS

Org. no. 989240099 Limited company (AS) Senja Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 885,000
Operating profit NOK 101,000
Equity NOK 40.8m
Incorporated 2005
Share capital NOK 136,000

BALLOGLASTER AS is registered as a limited company in Senja, Troms with organisation number 989240099. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 136,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i andre selskap og forvaltning av selskapets midler gjennom ulike finansielle plasseringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 885,000 in revenue and NOK 101,000 in operating profit.

Former names: SIRILUND AS

Key figures · 2025

Revenue
NOK 885,000
Operating profit
NOK 101,000
▲ +200 %
Equity
NOK 40.8m
▲ +0 %
Est. value
NOK 22.9m

Financial health · 2025

Liquidity
7.07
Very good
Current assets ÷ current liabilities
Profitability
2.8%
Weak
Return on total assets
Solidity
83.2%
Very good
Equity as a share of total capital

Who owns BALLOGLASTER AS?

BALLOGLASTER AS
NOK 885,000 rev. · NOK 101,000 profit

BALLOGLASTER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BALLOGLASTER AS own?

BALLOGLASTER AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BALLOGLASTER AS

Who owns BALLOGLASTER AS?

Ole-Martin Lund Andreassen is the largest registered owner, with 100.0%.

What is the revenue of BALLOGLASTER AS?

BALLOGLASTER AS had revenue of NOK 885,000 in 2025.

Where is BALLOGLASTER AS based?

BALLOGLASTER AS has its business address in Finnsnes.

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.