biztrac. BETA
COMPANY REGISTER PROFILE
987517913 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

SIP-TECH AS

Org. no. 987517913 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 82,000
Operating profit NOK 46,000
Equity NOK 202,000
Incorporated 2004
Share capital NOK 100,000

SIP-TECH AS is registered as a limited company in Oslo, Oslo with organisation number 987517913. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring og salg av bygg, salg av bygningsartikler samt levere arkitekttegninger til byggeprosjekter og konsulent bistand ifm dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 82,000 in revenue and NOK 46,000 in operating profit.

Former names: OSTERBLOMEN AS

Key figures · 2025

Revenue
NOK 82,000
▲ +47 %
Operating profit
NOK 46,000
▲ +1529 %
Equity
NOK 202,000
▲ +21 %
Est. value
NOK 254,000

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
12.5%
Good
Return on total assets
Solidity
55.1%
Very good
Equity as a share of total capital

Who owns SIP-TECH AS?

SIP-TECH AS
NOK 82,000 rev. · NOK 46,000 profit

SIP-TECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIP-TECH AS

Who owns SIP-TECH AS?

Rune Georg Herwig is the largest registered owner, with 100.0%.

What is the revenue of SIP-TECH AS?

SIP-TECH AS had revenue of NOK 82,000 in 2025.

Who is the general manager of SIP-TECH AS?

Rune Georg Herwig is registered as general manager of SIP-TECH AS.

Where is SIP-TECH AS based?

SIP-TECH 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 03.10.2026.

Report a problem

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