BIZTRAC BETA
Computer consultancy and computer facilities management activities

SPÆREN CONSULTING AS

Org. no. 923685332 Limited company (AS) Nordre Follo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK 11,000
Equity NOK 57,000
Incorporated 2019
Share capital NOK 30,000

SPÆREN CONSULTING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 923685332. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å hjelpe kunder med deres digitale forretningsløsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK 11,000
Equity
NOK 57,000
Est. value
NOK 73,000

Financial health · 2025

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

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

Who owns SPÆREN CONSULTING AS?

TEODOR SPÆREN
SPÆREN CONSULTING AS
NOK 16,000 rev. · NOK 11,000 profit

SPÆREN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPÆREN CONSULTING AS

Who owns SPÆREN CONSULTING AS?

TEODOR SPÆREN is the largest registered owner, with 100.0%.

What is the revenue of SPÆREN CONSULTING AS?

SPÆREN CONSULTING AS had revenue of NOK 16,000 in 2025.

Who is the general manager of SPÆREN CONSULTING AS?

Teodor Spæren is registered as general manager of SPÆREN CONSULTING AS.

Where is SPÆREN CONSULTING AS based?

SPÆREN CONSULTING AS has its business address in Kråkstad.

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.