BIZTRAC BETA
Civil engineering activities

OBF TEKNISK AS

Org. no. 996558347 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 88,000
Operating profit NOK 33,000
Equity NOK 437,000
Incorporated 2011
Share capital NOK 150,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OBF TEKNISK AS is registered as a limited company in Oslo, Oslo with organisation number 996558347. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2011. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Tilby teknisk relaterte tjenester til eiendomsbransjen i eget navn eller ved annet selskap, samt å delta eller erverve aksjer i selskaper med samme formål eller som har annen virksomhet som naturlig faller inn under formålet.”. The most recent filed accounts, for the 2024 financial year, show NOK 88,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2024

Revenue
NOK 88,000
Operating profit
NOK 33,000
Equity
NOK 437,000
Est. value
NOK 377,000

Financial health · 2024

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

Who owns OBF TEKNISK AS?

OSLO OG OMEGN BOLIGFORVALTNING AS
OBF TEKNISK AS
NOK 88,000 rev. · NOK 33,000 profit

OBF TEKNISK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OBF TEKNISK AS

Who owns OBF TEKNISK AS?

OSLO OG OMEGN BOLIGFORVALTNING AS is the largest registered owner, with 100.0%.

What is the revenue of OBF TEKNISK AS?

OBF TEKNISK AS had revenue of NOK 88,000 in 2024.

Where is OBF TEKNISK AS based?

OBF TEKNISK 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.